git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: opticyclic <opticyclic@gmail.com>
To: git@vger.kernel.org
Subject: Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests
Date: Wed, 29 Feb 2012 12:19:45 -0500	[thread overview]
Message-ID: <CAM=oOO2i-9zraF-YG5YzvZEmN1eXTnQfhJ-eMF04NP7HGtf41w@mail.gmail.com> (raw)

Firstly, why is there no Bug Tracker such as JIRA for the git project?
This mailing list is next to useless for users since searching is
difficult, as is commenting and voting.

Secondly, since one of the alleged reasons for creating git was to not
have to deal with patches, why are pull requests disable and patches
sent to this mailing list?!
I have read https://github.com/gitster/git/blob/master/Documentation/SubmittingPatches
and it doesn't explain it.

I'm sure I don't have to tell you that GitHub has discussions on pull
requests, which are easier to view than the mailing list archives.

So why is it done in the current way?

             reply	other threads:[~2012-02-29 17:19 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 17:19 opticyclic [this message]
2012-02-29 18:23 ` Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests Brian Gernhardt
2012-02-29 18:53 ` Junio C Hamano
2012-02-29 22:53   ` Jonathan Nieder
2012-02-29 23:58     ` Andrew Ardill
2012-03-01  0:37       ` Greg Troxel
2012-03-01  0:45         ` Andrew Ardill
2012-03-01  0:50           ` Junio C Hamano
2012-03-01  1:05             ` Andrew Ardill
2012-03-01  1:05           ` Junio C Hamano
2012-03-01  1:20             ` Andrew Ardill
2012-03-01  5:16           ` Miles Bader
2012-03-01  5:40             ` Andrew Ardill
2012-03-01 16:52         ` Scott Chacon
2012-03-01 20:23           ` Junio C Hamano
2012-03-01 11:29       ` Thomas Rast
2012-03-01 11:54         ` Ævar Arnfjörð Bjarmason
2012-03-01 12:46           ` Andrew Ardill
2012-03-01 12:28         ` Andrew Ardill
2012-03-01 17:10         ` Junio C Hamano
2012-03-02  4:03           ` Neal Kreitzinger
2012-03-02  4:19             ` Jonathan Nieder
2012-03-02  4:21               ` Junio C Hamano
2012-03-02  5:50               ` Neal Kreitzinger
2012-03-02  6:25                 ` Jonathan Nieder
2012-03-02  7:03                 ` Junio C Hamano
2012-03-02 14:18                   ` Andreas Ericsson
2012-03-02 16:45                     ` Junio C Hamano
2012-03-07  8:03                       ` Andrew Ardill
2012-03-07  9:52                         ` Vincent van Ravesteijn
2012-03-07 13:04                   ` Joern Huxhorn
2012-03-07 13:53                     ` Jonathan Nieder
2012-03-07 14:47                       ` Joern Huxhorn
2012-03-07 15:08                     ` Pau Garcia i Quiles
2012-03-07 17:18                   ` Phil Hord
2012-02-29 19:18 ` Carlos Martín Nieto
2012-02-29 21:37 ` Sitaram Chamarty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAM=oOO2i-9zraF-YG5YzvZEmN1eXTnQfhJ-eMF04NP7HGtf41w@mail.gmail.com' \
    --to=opticyclic@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).