git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed

From: "Aaron S. Meurer" <asmeurer@gmail.com>
To: git@vger.kernel.org
Subject: git bisect problems/ideas
Date: Sat, 15 Jan 2011 00:33:12 -0700	[thread overview]
Message-ID: <855249CA-A006-475C-8F96-EFD614795064@gmail.com> (raw)

First off, do you guys have an issue tracker?  I asked on IRC, and someone told me that he didn't think you did, and to just post here.  After searching your websites, as far as I can tell he was right, though this is amazing to me that you can handle a project like this without an issue tracker.  If you guys really do, then sorry.  I would rather post this there than here (though if you really do, please make it more findable!)

I just noticed this error/bug:

git checkout test
git bisect start 
<do some bisecting>
git branch -D test
<finish bisecting>
git bisect reset

And it gives an error, because test has been deleted.  This is in 1.7.3.5.  Now, I looked through the log of the current master of git to see if anything has been done about this, and all I noticed was the commit 3bb8cf88247db5, which essentially improves the error message.  

Now, this is good, because it seemed to me above that I was stuck bisecting until I recreated the test branch.  I did not realize the git bisect <commit> syntax until later.  

But this has brought me to bother you guys about something that has been bugging me for a while. I hate git bisect reset.  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 just stops the bisecting process, but leaves me where I am (like a shortcut to git bisect reset HEAD).  This would be much more symmetric with git bisect start.

While we are on the topic of bisecting, I have another issue.  Can we remove the restriction that a "bad" commit come after a "good" commit?  I'd say about 70% of the time I use bisect to find a commit that fixes a bug, not breaks it.  Whenever this happens, I have to bend my mind over backwards to remind myself that the good behavior is really "bad" and the bad behavior is really "good".  Is there a reason that git bisect can't just introspect from which comes earlier and which comes later to see which is "good" or "bad" (instead of just raising an error when they are in the "wrong" order)?

Aaron Meurer

next             reply	other threads:[~2011-01-15  7:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15  7:33 Aaron S. Meurer [this message]
2011-01-17  9:38 ` git bisect problems/ideas 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
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=855249CA-A006-475C-8F96-EFD614795064@gmail.com \
    --to=asmeurer@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

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).