git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-bisect is magical

From
Andreas Ericsson <ae@op5.se>
Date
Jan 9, 2006, 23:39 UTC
Message-ID
<43C2F422.9070209@op5.se>
In-Reply-To
<dpuoqf$3rp$1@sea.gmane.org>
walt wrote:
Show 11 quoted lines
> 
> I have one minor suggestion for howto/isolate-bugs-with-bisect.
> Linus states:
>        git bisect good ORIG_HEAD       <- mark ORIG_HEAD as good (or
>                                            whatever other known-good
>                                            thing you booted last)
> 
> Well, in my case, I new the last good kernel was *two* updates ago,
> so ORIG_HEAD wasn't the right thing to use.  I had to guess what
> to type instead of 'ORIG_HEAD'.
> 

It would be neat if resets could optionally be stored as unannotated tags as well as ORIG_HEAD, with a date and time in the tag-name.

	git tag reset-$(date '+%F_%H.%M.%S')

works fine for me, although I expect the quibbling about the date-format will never stop. I'll get going on it tomorrow unless I get some seriously vehement requests not to, or someone beats me to it.

If someone *does* beat me to it, perhaps "git reset --clean-tags" should be implemented as well?

Show 5 quoted lines
> Which leads to one more question:  I have my kernel configured to
> add the -gxxxxxxxx localversion string to the kernel name.  I took
> a wild guess that the xxxxxxxx was the right thing to substitute
> for 'ORIG_HEAD' and I got lucky.  But what about someone who
> doesn't know the magic 'xxxxxxxx' to use? 

I expect you remember the date and approximate time you built it so the --tag option should work fairly well there, I'd say. Otherwise, tagging the build like you do is a very good idea.

Show 7 quoted lines
>If I didn't know enough
> to keep a week's worth of daily kernel-builds with the 'xxxxxxxx'
> to guide me, would I still be able to do what I did today?
> (For example, if this had been a 'git' bug instead of a kernel bug,
> I don't think I could have figured out how to use git-bisect to find
> the bug -- could I?)
> 

Most likely not as easily, although it would have been fairly easy to mark the most recent tag as a known good build, or Linus' latest tree from upstream.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231
Previous: walt
Message 14 of 14 in “git-bisect is magical”
  1. waltJan 9, 2006
  2. Linus TorvaldsJan 9, 2006
  3. waltJan 10, 2006
  4. Linus TorvaldsJan 10, 2006
  5. Linus TorvaldsJan 10, 2006
  6. waltJan 10, 2006
  7. Linus TorvaldsJan 10, 2006
  8. waltJan 11, 2006
  9. Junio C HamanoJan 11, 2006
  10. Linus TorvaldsJan 11, 2006
  11. waltJan 11, 2006
  12. Sytse WielingaJan 12, 2006
  13. waltJan 12, 2006
  14. Andreas EricssonJan 9, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.