lkml.org 
[lkml]   [2005]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Arrr! Linux v2.6.14-rc2


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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2009-11-18 23:46    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site