From: Linus Torvalds <torvalds@osdl.org>
To: Sean <seanlkml@sympatico.ca>
Cc: Jan Dittmer <jdittmer@ppp0.net>,
Alexander Nyberg <alexn@telia.com>,
Gene Heskett <gene.heskett@verizon.net>,
linux-kernel@vger.kernel.org
Subject: Re: Arrr! Linux v2.6.14-rc2
Date: Tue, 20 Sep 2005 10:02:53 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0509200959220.2553@g5.osdl.org> (raw)
In-Reply-To: <BAYC1-PASMTP0390B5ABE91EDE56C81EDBAE950@cez.ice>
On Tue, 20 Sep 2005, Sean wrote:
>
> That's a good point. Guess it would be useful if the HEAD commit was
> documented along with each -gitX release.
It is. Just get the "id" file that is associated with a snapshot, and it
gives the git commit ID for that state.
So for example, the 2.6.14-rc1-git3 snapshot is associated with the ID
file patch-2.6.14-rc1-git3.id, which contains
v2.6/snapshots(0)$ cat patch-2.6.14-rc1-git3.id
065d9cac98a5406ecd5a1368f8fd38f55739dee9
so once you know that something broke between rc1-git3 and rc1-git4, you
can now do
git bisect start
git bisect good 065d9cac98a5406ecd5a1368f8fd38f55739dee9
git bisect bad bc5e8fdfc622b03acf5ac974a1b8b26da6511c99
and off you go..
Linus
next prev parent reply other threads:[~2005-09-20 17:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 3:22 Arrr! Linux v2.6.14-rc2 Linus Torvalds
2005-09-20 3:44 ` Nick Piggin
2005-09-20 4:50 ` Gene Heskett
2005-09-20 13:31 ` Patrick McFarland
2005-09-20 14:05 ` Gene Heskett
2005-09-20 14:10 ` Russell King
2005-09-20 14:25 ` Gene Heskett
[not found] ` <56402.10.10.10.28.1127229646.squirrel@linux1>
2005-09-20 15:20 ` Sean
2005-09-20 20:45 ` Gene Heskett
2005-09-20 20:57 ` Gene Heskett
2005-09-20 21:00 ` Matthew Dharm
2005-09-20 21:23 ` Gene Heskett
2005-09-20 21:39 ` Gene Heskett
2005-09-21 16:50 ` Gene Heskett
2005-09-21 18:28 ` Bill Davidsen
[not found] ` <44442.10.10.10.28.1127329602.squirrel@linux1>
2005-09-21 19:06 ` Sean
2005-09-20 15:29 ` Russell King
2005-09-20 15:32 ` Alexander Nyberg
[not found] ` <54562.10.10.10.28.1127230800.squirrel@linux1>
2005-09-20 15:40 ` Sean
2005-09-20 16:18 ` Jan Dittmer
[not found] ` <36267.10.10.10.28.1127233614.squirrel@linux1>
2005-09-20 16:26 ` Sean
2005-09-20 16:44 ` Jan Dittmer
[not found] ` <48312.10.10.10.28.1127235046.squirrel@linux1>
2005-09-20 16:50 ` Sean
2005-09-20 17:00 ` Jan Dittmer
2005-09-20 17:02 ` Linus Torvalds [this message]
[not found] ` <52797.10.10.10.28.1127236164.squirrel@linux1>
2005-09-20 17:09 ` Sean
[not found] ` <41938.10.10.10.28.1127252566.squirrel@linux1>
2005-09-20 21:42 ` using -gitX snapshot tags [was Re: Arrr! Linux v2.6.14-rc2] Sean
2005-09-20 17:09 ` Arrr! Linux v2.6.14-rc2 Alexey Dobriyan
2005-09-20 17:59 ` Horst von Brand
[not found] ` <59258.10.10.10.28.1127241246.squirrel@linux1>
2005-09-20 18:34 ` Sean
2005-09-20 18:48 ` Russell King
2005-09-21 0:43 ` Gene Heskett
2005-09-21 18:22 ` Bill Davidsen
2005-09-20 23:03 ` Martin J. Bligh
2005-09-20 23:11 ` Nish Aravamudan
2005-09-20 23:12 ` James Bottomley
2005-09-20 23:13 ` Martin J. Bligh
2005-09-21 22:51 ` Martin J. Bligh
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=Pine.LNX.4.58.0509200959220.2553@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=alexn@telia.com \
--cc=gene.heskett@verizon.net \
--cc=jdittmer@ppp0.net \
--cc=linux-kernel@vger.kernel.org \
--cc=seanlkml@sympatico.ca \
/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 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 NNTP newsgroup(s).