git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Aaron S. Meurer" <asmeurer@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Couder <christian.couder@gmail.com>, git@vger.kernel.org
Subject: Re: git bisect problems/ideas
Date: Wed, 19 Jan 2011 12:15:15 -0700	[thread overview]
Message-ID: <0F4E18EC-E67D-4C3E-BB5C-C8D8BA326C1D@gmail.com> (raw)
In-Reply-To: <7vd3nukqn8.fsf@alter.siamese.dyndns.org>

So if I care about this issue I should keep bumping it until it gets fixed?

Aaron Meurer

On Jan 18, 2011, at 11:34 AM, Junio C Hamano wrote:

> Christian Couder <christian.couder@gmail.com> writes:
> 
>> Well, bugs are usually fixed within days after they have been
>> reported. Otherwise they are usually documented in the code or in the
>> documentation or in the test suite (with test_expect_failure).
>> 
>> For the rest we rely on people remembering what happened and on
>> people's mailing list searching skills ;-)
> 
> Not really.
> 
> What we do is to take advantage of the fact that issues people do care
> about are important ones, and others that nobody cares about are not worth
> pursuing.
> 
> In a sense, "people forgetting" is a lot more important than "people
> remembering" to filter unimportant issues (issues that are so unimportant
> that even the original complainer does not bother to come back and
> re-raise it).

  parent reply	other threads:[~2011-01-19 19:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15  7:33 git bisect problems/ideas Aaron S. Meurer
2011-01-17  9:38 ` Christian Couder
2011-01-17 11:51   ` Jonathan Nieder
2011-01-17 13:38     ` SZEDER Gábor
2011-01-17 20:55       ` Jonathan Nieder
2011-01-18  9:05         ` Christian Couder
2011-01-17 18:27     ` Aaron S. Meurer
2011-01-17 18:23   ` Aaron S. Meurer
2011-01-18  9:04     ` Christian Couder
2011-01-18 18:34       ` Junio C Hamano
2011-01-19 13:15         ` Christian Couder
2011-01-19 19:15         ` Aaron S. Meurer [this message]
2011-01-19 19:29           ` Junio C Hamano
2011-01-19 19:44       ` Aaron S. Meurer
2011-01-21 13:18         ` Christian Couder
2011-01-21 22:04           ` Johannes Sixt
2011-01-22 14:52             ` Jakub Narebski

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=0F4E18EC-E67D-4C3E-BB5C-C8D8BA326C1D@gmail.com \
    --to=asmeurer@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).