From: Fernando J. Pereda <ferdy@ferdyx.org>
Date: Mon, 13 Feb 2006 09:58:59 GMT
Subject: Re: git-bisect problem
Message-ID: <20060213095859.GA17115@ferdyx.org>
In-Reply-To: <20060213015146.26e6c09d.akpm@osdl.org>

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