From: "Fernando J. Pereda" <ferdy@ferdyx.org>
To: git@vger.kernel.org
Subject: Re: git-bisect problem
Date: Mon, 13 Feb 2006 10:58:59 +0100 [thread overview]
Message-ID: <20060213095859.GA17115@ferdyx.org> (raw)
In-Reply-To: <20060213015146.26e6c09d.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
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
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-13 9:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 8:25 git-bisect problem Andrew Morton
2006-02-13 9:11 ` Junio C Hamano
2006-02-13 9:32 ` Andrew Morton
2006-02-13 9:39 ` Ryan Anderson
2006-02-13 9:51 ` Andrew Morton
2006-02-13 9:58 ` Fernando J. Pereda [this message]
2006-02-13 10:22 ` Luben Tuikov
2006-02-13 10:23 ` Luben Tuikov
2006-02-13 12:21 ` cat-file (was Re: git-bisect problem) Joshua N Pritikin
2006-02-13 10:14 ` git-bisect problem Ryan Anderson
2006-02-13 10:25 ` Andrew Morton
2006-02-13 16:44 ` Linus Torvalds
2006-02-13 10:40 ` Luben Tuikov
2006-02-13 10:44 ` Andrew Morton
2006-02-14 0:33 ` Junio C Hamano
2006-02-13 10:08 ` Junio C Hamano
2006-02-13 10:19 ` Andrew Morton
2006-02-14 0:32 ` Junio C Hamano
2006-02-14 0:56 ` Andrew Morton
2006-02-14 1:14 ` Linus Torvalds
2006-02-14 1:15 ` Petr Baudis
2006-02-14 1:27 ` Petr Baudis
2006-02-14 1:52 ` Junio C Hamano
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=20060213095859.GA17115@ferdyx.org \
--to=ferdy@ferdyx.org \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.