From: Daniel Barkalow <barkalow@iabervon.org>
To: git@vger.kernel.org
Subject: [RFC] format-patch stuff
Date: Sat, 12 May 2007 11:36:54 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705121109520.18541@iabervon.org> (raw)
It would be nice if git-format-patch would generate a [PATCH 0/n] message
at the start of the series if some option were given. This would, of
course, have to be editted afterwards to include actual information, but
it would at least be pre-generated in series and with the configured
headers and such.
Shouldn't the format.headers configuration automatically apply the correct
line termination? Currently, you need to know to put in \r\n at the end of
each one, and the example isn't even right (only puts \n).
Once we've got library support for remotes configuration, it would be nice
to be able to have "mailto:" remotes with emailed patch configuration
stuff per-destination.
-Daniel
*This .sig left intentionally blank*
next reply other threads:[~2007-05-12 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 15:36 Daniel Barkalow [this message]
2007-05-12 20:24 ` [RFC] format-patch stuff Junio C Hamano
2007-05-12 21:40 ` Frank Lichtenheld
2007-05-12 22:54 ` david
2007-05-12 23:03 ` 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=Pine.LNX.4.64.0705121109520.18541@iabervon.org \
--to=barkalow@iabervon.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 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).