From: Jonathan Nieder <jrnieder@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: "Aaron S. Meurer" <asmeurer@gmail.com>, git@vger.kernel.org
Subject: Re: git bisect problems/ideas
Date: Mon, 17 Jan 2011 05:51:33 -0600 [thread overview]
Message-ID: <20110117115133.GA29207@burratino> (raw)
In-Reply-To: <AANLkTikNzpCwEieV8sXXctMm+DR69fkLfCF+F3xB6b-k@mail.gmail.com>
Hi,
> Aaron S. Meurer wrote:
>> 90% of the time I do not
>> want to go back to where I started bisecting. I would much prefer to just
>> have a git bisect stop command
[which does "git bisect reset HEAD"]
FWIW I like the idea. I end up using "git bisect reset" by accident
from time to time and it is almost never what I want, especially
after working on something else for a few days[1].
My only worry is that it could be confusing --- what if a person,
intending to run "git bisect reset", runs "git bisect stop" instead?
To mitigate that, the stop subcommand could print the name of the
start commit so such a user knows what to check out to get back to
a familiar state.
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...
Ciao,
Jonathan
[1] compare am --abort:
http://thread.gmane.org/gmane.comp.version-control.git/164002
next prev parent reply other threads:[~2011-01-17 11:52 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 [this message]
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
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=20110117115133.GA29207@burratino \
--to=jrnieder@gmail.com \
--cc=asmeurer@gmail.com \
--cc=christian.couder@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).