Re: git-bisect problem

From: Fernando J. Pereda <ferdy@ferdyx.org>
Date: 2006-02-13 20:58:59
On Mon, Feb 13, 2006 at 01:51:46AM -0800, Andrew Morton wrote:
| Assuming I find the bad commit, how do I extract it as a patch?
| 
| I tried
| 
| git-format-patch -o ~/a 386093ef9a6c88576d8b418bf1c8616d5e410a20 git-netdev-all
| 
| and that chewed 10 minutes CPU time and produced no output, so I killed it.

This gives you the whole info about the commit, including a patch:

git cat-file commit 386093ef9a6c88576d8b418bf1c8616d5e410a20

Cheers,
Ferdy

-- 
Fernando J. Pereda Garcimartín
Gentoo Developer (Alpha,net-mail,mutt,git)
20BB BDC3 761A 4781 E6ED  ED0B 0A48 5B0C 60BD 28D4


-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Mon Feb 13 20:59:36 2006

This archive was generated by hypermail 2.1.8 : 2006-02-13 20:59:46 EST