From: Andreas Ericsson <ae@op5.se>
To: walt <wa1ter@myrealbox.com>
Cc: git@vger.kernel.org
Subject: Re: git-bisect is magical
Date: Tue, 10 Jan 2006 00:39:14 +0100 [thread overview]
Message-ID: <43C2F422.9070209@op5.se> (raw)
In-Reply-To: <dpuoqf$3rp$1@sea.gmane.org>
walt wrote:
>
> 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?
> 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.
>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
prev parent reply other threads:[~2006-01-09 23:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 22:41 git-bisect is magical walt
2006-01-09 23:38 ` 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 [this message]
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=43C2F422.9070209@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=wa1ter@myrealbox.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.