From: Junio C Hamano <junkio@cox.net>
To: Jon Loeliger <jdl@freescale.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] Add the --numbered-files option to git-format-patch.
Date: Wed, 06 Jun 2007 00:50:25 -0700 [thread overview]
Message-ID: <7vps497c8u.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1181074013.2585.14.camel@ld0161-tx32> (Jon Loeliger's message of "Tue, 05 Jun 2007 15:06:53 -0500")
Jon Loeliger <jdl@freescale.com> writes:
> With this option, git-format-patch will generate simple
> numbered files as output instead of the default using
> with the first commit line appended.
>
> This simplifies the ability to generate an MH-style
> drafts folder with each message to be sent.
I'll take the patch but wouldn't something like:
git-format-patch --stdout $args |
FILENO=7 formail -s sh -c 'cat >.junk/$FILENO'
be equivalent to
git-format-patch -o .junk/ --numbered-files --start-number=7 $args
and more flexible?
prev parent reply other threads:[~2007-06-06 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 20:06 [PATCH] Add the --numbered-files option to git-format-patch Jon Loeliger
2007-06-06 7:50 ` Junio C Hamano [this message]
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=7vps497c8u.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jdl@freescale.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).