From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: opticyclic <opticyclic@gmail.com>, git@vger.kernel.org
Subject: Re: Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests
Date: Wed, 29 Feb 2012 16:53:04 -0600 [thread overview]
Message-ID: <20120229225304.GA9099@burratino> (raw)
In-Reply-To: <7vhay9tqs6.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> opticyclic <opticyclic@gmail.com> writes:
>> Firstly, why is there no Bug Tracker such as JIRA for the git project?
>
> Probably because nobody volunteered to set-up, actively de-dupe, triage
> and maintain it in general.
By the way, my usual offer/shameless plug[*] still stands: anyone who
can stand the interface is welcome to file, triage, and work on bugs
in the bugtracker at <http://bugs.debian.org/src:git>, as long as it
seems possible that your bugs might also affect Debian.
"Work on" usually means "forward to the git mailing list", but maybe
having a bug number is a comfort to some people. ;-) See
<http://www.debian.org/Bugs/Reporting> for instructions.
All that said, that is still not The Bug Tracker for the git project.
I would not want it advertised on git-scm.com until we have had some
more practice dealing with outside bugs, and maybe more contributors
sorting through them.
It may be that others provide a similar service.
Hope that clarifies a little,
Jonathan
[*] http://thread.gmane.org/gmane.comp.version-control.git/181336/focus=181402
next prev parent reply other threads:[~2012-02-29 22:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 17:19 Why Is There No Bug Tracker And Why Are Patches Sent Instead Of Pull Requests opticyclic
2012-02-29 18:23 ` Brian Gernhardt
2012-02-29 18:53 ` Junio C Hamano
2012-02-29 22:53 ` Jonathan Nieder [this message]
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=20120229225304.GA9099@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=opticyclic@gmail.com \
/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).