All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Gilger <heipei@hackvalue.de>
To: git@vger.kernel.org
Subject: Re: git maintenance bug tracker sooner better than later
Date: Fri, 6 Feb 2009 16:30:16 +0000 (UTC)	[thread overview]
Message-ID: <slrngoopcn.14u8.heipei@macbook.lan> (raw)
In-Reply-To: 87skmrhf5i.fsf@jidanni.org

On 2009-02-06, jidanni@jidanni.org <jidanni@jidanni.org> wrote:
> With a bug tracker, at least one knows somebody saw something for
> sure, and it didn't just float by. That way one could register items
> into it on one's good days, and then take a break, which I am going to
> do now. Thanks.

And what "bugs" would you file? If I look at your patch-series which 
consists of oneliner documentation nitpicking, I don't even want to 
imagine how much these would get blown up by a web-based bug-tracker.

The web-based is the second part: When working on/with *git*, a 
command-line tool, I naturally work in a terminal, and I *don't* want to 
fire up a webbrowser to communicate something as simple as a bug. Also 
bug-trackers tend to attract all sorts of people who don't really think 
or try to find bugs before submitting them. Those sorts of people 
probably already file bugs for git and the distribution-maintainers then 
tell them to report the problem upstream (i.e.: here) or do it 
themselves.

-- 
Johannes Gilger <heipei@hackvalue.de>
http://hackvalue.de/heipei/
GPG-Key: 0x42F6DE81
GPG-Fingerprint: BB49 F967 775E BB52 3A81  882C 58EE B178 42F6 DE81

      reply	other threads:[~2009-02-06 16:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 19:07 git maintenance bug tracker sooner better than later jidanni
2009-02-02 22:07 ` Christian MICHON
2009-02-03 10:05 ` Nanako Shiraishi
2009-02-03 13:38   ` Teemu Likonen
2009-02-03 14:42     ` Johannes Schindelin
2009-02-04  0:28       ` jidanni
2009-02-06 12:33         ` Johannes Gilger
2009-02-06 12:56         ` Andreas Ericsson
2009-02-06 13:24           ` jidanni
2009-02-06 16:30             ` Johannes Gilger [this message]

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

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

  git send-email \
    --in-reply-to=slrngoopcn.14u8.heipei@macbook.lan \
    --to=heipei@hackvalue.de \
    --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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.