From: Daniel Barkalow <barkalow@iabervon.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Bert Wesarg <bert.wesarg@googlemail.com>,
Git Mailing List <git@vger.kernel.org>,
Ryan Anderson <ryan@michonline.com>
Subject: Re: format-patch --cc and send-mail --s-o-b-cc don't play nice together
Date: Tue, 29 Apr 2008 18:28:24 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.1.00.0804291756070.19665@iabervon.org> (raw)
In-Reply-To: <7v8wyw7349.fsf@gitster.siamese.dyndns.org>
On Tue, 29 Apr 2008, Junio C Hamano wrote:
> "Bert Wesarg" <bert.wesarg@googlemail.com> writes:
>
> > the --cc option from format-patch adds a Cc: header to the mail where
> > multiple recipients are put into a new line, separated by commas.
>
> I am not sure if --cc ever made sense to be given to format-patch. It is
> not a tool to send e-mails, which send-email is.
But part of preparing patches for e-mail submission is often figuring out
where to send them. I think the common use of format-patch is to generate
the series, import it into some MUA (I actually append it to my "postponed
messages" mbox for Alpine), edit the messages to add any commentary needed
outside of the commit message, and send them, going through the user's
normal outgoing email path. For this purpose, it makes sense to be able to
get git to produce anything that is standard for patch submission in the
project, so that the user doesn't have to edit them more than necessary.
I think that it would make sense for format-patch to handle
--signed-off-by-cc itself, since this is clearly generating useful
information for composing the email out of git's information about the
commits.
> > Unfortunately send-mail with the --signed-off-by-cc option can't parse
> > these lines.
>
> Isn't --signed-off-by-cc a completely unrelated feature, where it gives
> carbon copies to people who signed off the patch? Why does the option
> need to read from existing CC: header of the material the command is told
> to send out?
It also Cc's people listed in Cc: lines in the commit message, which I'd
guess is where it's getting confused. But it also makes sense that people
might want to determine who to send each patch to individually, put it in
the patch in the RFC823-compliant fashion, additionally include people in
Signed-off-by: lines, and send the whole batch off, in which case
send-email would need to know how to handle existing Cc: headers which may
be wrapped.
-Daniel
*This .sig left intentionally blank*
prev parent reply other threads:[~2008-04-29 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 13:57 format-patch --cc and send-mail --s-o-b-cc don't play nice together Bert Wesarg
2008-04-29 21:39 ` Junio C Hamano
2008-04-29 22:11 ` Bert Wesarg
2008-04-29 22:28 ` Daniel Barkalow [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=alpine.LNX.1.00.0804291756070.19665@iabervon.org \
--to=barkalow@iabervon.org \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ryan@michonline.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