git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: Christian Couder <christian.couder@gmail.com>,
	"Aaron S. Meurer" <asmeurer@gmail.com>,
	git@vger.kernel.org
Subject: Re: git bisect problems/ideas
Date: Mon, 17 Jan 2011 14:55:42 -0600	[thread overview]
Message-ID: <20110117205542.GA21507@burratino> (raw)
In-Reply-To: <20110117133843.GA23625@neumann>

SZEDER Gábor wrote:
> On Mon, Jan 17, 2011 at 05:51:33AM -0600, Jonathan Nieder wrote:
>> Christian Couder wrote:

>>> Yeah, many people find it difficult to reverse the meaning of "bad"
>>> and "good" when looking for a fix. There were some suggestions at some
>>> points to do something about it. Some of the suggestions were to use
>>> some aliases for "good" and "bad", but there was no agreement. Other
>>> suggestions had a patch attached but the patch was not good enough or
>>> something.
>>
>> Any pointers to such a discussion or patch?  Maybe whatever small
>> detail caused it to be forgotten could be fixed...
>
> http://thread.gmane.org/gmane.comp.version-control.git/86063

A better link for those who are thinking of picking up the topic might
be [1].

The problems were:

 - error messages refer to "good" and "bad" with the original,
   unreversed meaning, which could be confusing (but see later in the
   thread!).
 - "git bisect visualize" doesn't get the memo about the new worldview.
 - it seems that some people lost interest after a while.

None of these seems totally fatal --- as a new feature, it would not
be breaking anyone's workflow, especially if the potentially confusing
bits are clearly documented.

Thanks.

[1] http://thread.gmane.org/gmane.comp.version-control.git/86089/focus=86161

  reply	other threads:[~2011-01-17 20:56 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 [this message]
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
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=20110117205542.GA21507@burratino \
    --to=jrnieder@gmail.com \
    --cc=asmeurer@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=szeder@ira.uka.de \
    /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).