From: Andreas Ericsson <ae@op5.se>
To: ltuikov@yahoo.com
Cc: git@vger.kernel.org
Subject: Re: [RFC] git-format-patch options
Date: Mon, 21 Nov 2005 18:59:20 +0100 [thread overview]
Message-ID: <43820AF8.5060208@op5.se> (raw)
In-Reply-To: <20051121173603.73700.qmail@web31806.mail.mud.yahoo.com>
Luben Tuikov wrote:
> --- Andreas Ericsson <ae@op5.se> wrote:
>
>
>>Please don't. git-format-patch is generally used to send
>
>
> Ok, so then when I want to extract a single commit into a patch in a patch format, I loosely do
> (scripted):
>
> git-rev-list --pretty=raw --max-count=1 <commit-ish>
>
> Then I record the parent <parent> of the commit-ish and do:
>
> git-format-patch [output options] <parent>..<commit-ish>
>
> Which gives me the commit with id <commit-ish> as a
> formatted patch.
>
> Is there an alernative to this, as opposed to the two
> step procedure above?
>
Here's how to automate it.
git format-patch $(git rev-list --max-count=2 <commit-ish> | tail -n
1)..<commit-ish>
Either way, you need to know <commit-ish>, but this format should be
fairly easy to add to git-format-patch. If you do, please let the user
specify the --max-count (but default to 1) so it can be used to extract
a series of patches rather than just one.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-11-21 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 16:25 [RFC] git-format-patch options Luben Tuikov
2005-11-21 16:44 ` Andreas Ericsson
2005-11-21 17:36 ` Luben Tuikov
2005-11-21 17:59 ` Andreas Ericsson [this message]
2005-11-21 18:27 ` Luben Tuikov
2005-11-21 19:11 ` Ryan Anderson
2005-11-22 1:53 ` Luben Tuikov
2005-11-21 19:27 ` Junio C Hamano
2005-11-22 6:26 ` Luben Tuikov
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=43820AF8.5060208@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=ltuikov@yahoo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).