[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <05ad01c77ba8$cd753040$294b82ce@stuartm>
Date: Tue, 10 Apr 2007 15:45:33 -0400
From: "Stuart MacDonald" <stuartm@...necttech.com>
To: "'Paolo Ornati'" <ornati@...twebnet.it>
Cc: <linux-kernel@...r.kernel.org>
Subject: RE: Alternative to 'git bisect visualize'?
From: Paolo Ornati [mailto:ornati@...twebnet.it]
> I think this should work:
>
> 1) look at "git-bisect log" and take the last good/bad pair
>
> 2) "cat .git/refs/heads/bisect" to see where you are now
>
> 3) git-log --pretty=oneline GOOD..BAD
>
> 4) search for the current commit (found in #2) with "/CURRENT_COMMIT",
> now move around and choose another commit to test
>
> 5) git-reset --hard COMMIT_TO_TEST
That is exactly what I needed, many many thanks. I have moved off the
broken area of commits and am back into bisecting.
Where would be the appropriate place to submit this as a feature
request, to complement "git bisect visualize"; git, LKML or somewhere
else? I'm picturing an ncurses/menuconfig-style app.
..Stu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists