From: "Dan McGee" <dpmcgee@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-format-patch(1)- add note about creating patch for single commit
Date: Sun, 19 Oct 2008 00:26:35 -0500 [thread overview]
Message-ID: <449c10960810182226t5e2ae1ay4b53656a7cac4606@mail.gmail.com> (raw)
In-Reply-To: <7v1vyd9n3d.fsf@gitster.siamese.dyndns.org>
On Sun, Oct 19, 2008 at 12:21 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Dan McGee <dpmcgee@gmail.com> writes:
>
>> Signed-off-by: Dan McGee <dpmcgee@gmail.com>
>> ---
>>
>> I thought this would be helpful because it took me the beter part of an hour
>> to find a solution instead of specifying C~1..C or other crazy things. The
>> current documentation just leaves you hanging when what you really want is
>> just one formatted patch.
>>
>> If there any suggestions on better wording, feel free to resubmit or whatever-
>> I just felt like this should be documented somewhere.
>>
>> Documentation/git-format-patch.txt | 4 +++-
>> 1 files changed, 3 insertions(+), 1 deletions(-)
>>
>> diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
>> index adb4ea7..8518c33 100644
>> --- a/Documentation/git-format-patch.txt
>> +++ b/Documentation/git-format-patch.txt
>> @@ -46,7 +46,9 @@ applies to that command line and you do not get "everything
>> since the beginning of the time". If you want to format
>> everything since project inception to one commit, say "git
>> format-patch \--root <commit>" to make it clear that it is the
>> -latter case.
>> +latter case. If you want to format only a single commit, say "git
>> +format-patch <commit>^!" (which excludes all parent revisions of the
>> +specified commit).
>>
>> By default, each output file is numbered sequentially from 1, and uses the
>> first line of the commit message (massaged for pathname safety) as
>
> Heh, a more natural way to say that is:
>
> git format-patch -1 $that_one
>
> That uses the first option described in the documentation:
>
> -<n>::
> Limits the number of patches to prepare.
Wow, had no idea about that option. :)
Given that I didn't even notice this option when I did go to the
manpage, what if my above change was instead reworked a bit:
>> +latter case. If you want to format only a single commit, say "git
>> +format-patch -1 <commit>" .
next prev parent reply other threads:[~2008-10-19 5:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 4:54 [PATCH] git-format-patch(1)- add note about creating patch for single commit Dan McGee
2008-10-19 5:21 ` Junio C Hamano
2008-10-19 5:26 ` Dan McGee [this message]
2008-10-19 5:33 ` 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=449c10960810182226t5e2ae1ay4b53656a7cac4606@mail.gmail.com \
--to=dpmcgee@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).