public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: walt <wa1ter@myrealbox•com>
To: git@vger•kernel.org
Subject: git-bisect is magical
Date: Mon, 09 Jan 2006 14:41:18 -0800	[thread overview]
Message-ID: <dpuoqf$3rp$1@sea.gmane.org> (raw)

Arthur C. Clarke's Third Law states:  Any sufficiently advanced
technology is indistinguishable from magic.

You guys have done it -- I can't distinguish git-bisect from
magic.  It's wonderful, and thank you!

I used it for the first time this morning to find the commit
which caused some kernel breakage.  I just sent off an email
to the developer whose commit did the breakage, and it only
took me about 45 minutes.  (Now all I need to do is sit back
and wait for his reply saying 'You're an idiot!')

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

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

Thanks!

next             reply	other threads:[~2006-01-09 22:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 22:41 walt [this message]
2006-01-09 23:38 ` git-bisect is magical Linus Torvalds
2006-01-10 19:19   ` walt
2006-01-10 19:42     ` Linus Torvalds
2006-01-10 19:45       ` Linus Torvalds
2006-01-10 20:43         ` walt
2006-01-10 21:17           ` Linus Torvalds
2006-01-11  1:50             ` walt
2006-01-11  2:47               ` Junio C Hamano
2006-01-11  2:58               ` Linus Torvalds
2006-01-11 18:07                 ` walt
2006-01-12 21:59                   ` Sytse Wielinga
2006-01-12 23:49                     ` walt
2006-01-09 23:39 ` Andreas Ericsson

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='dpuoqf$3rp$1@sea.gmane.org' \
    --to=wa1ter@myrealbox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox