Git development
 help / color / mirror / Atom feed
From: "Bert Wesarg" <bert.wesarg@googlemail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Git Mailing List" <git@vger.kernel.org>,
	"Daniel Barkalow" <barkalow@iabervon.org>,
	"Ryan Anderson" <ryan@michonline.com>
Subject: Re: format-patch --cc and send-mail --s-o-b-cc don't play nice together
Date: Wed, 30 Apr 2008 00:11:18 +0200	[thread overview]
Message-ID: <36ca99e90804291511m619c8373j5e79edab2e57f644@mail.gmail.com> (raw)
In-Reply-To: <7v8wyw7349.fsf@gitster.siamese.dyndns.org>

On Tue, Apr 29, 2008 at 11:39 PM, Junio C Hamano <gitster@pobox.com> 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.
AFAIK, this option is not in the master branch.

>
>  > 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?
No, it scans Cc: lines (header and body) too and add these to the cc
list (in the body since abec100c3382f7d7b759f915a86e9773277263b6).

Bert

  reply	other threads:[~2008-04-29 22:12 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 [this message]
2008-04-29 22:28   ` Daniel Barkalow

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=36ca99e90804291511m619c8373j5e79edab2e57f644@mail.gmail.com \
    --to=bert.wesarg@googlemail.com \
    --cc=barkalow@iabervon.org \
    --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