git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: cover letter and cc list
Date: Mon, 23 Mar 2015 09:18:40 +0100	[thread overview]
Message-ID: <20150323081840.GB9332@aepfle.de> (raw)
In-Reply-To: <xmqqpp83ee2z.fsf@gitster.dls.corp.google.com>

On Fri, Mar 20, Junio C Hamano wrote:

> Olaf Hering <olaf@aepfle.de> writes:
> 
> > What does it take to send the cover letter to all people which are
> > listed in the Cc: list of the following patches? Each patch has a
> > different Cc: list. The "git send-email --help" command suggests that
> > this cmdline should do it. But the cover letter goes just to the address
> > listed in --to=:
> >
> > env TMPDIR=/dev/shm LC_ALL=C git send-email -M --stat --annotate \
> >         --cover-letter --cc-cover --to=$address \
> >         $base..$head
> 
> First step is not to drive format-patch from within send-email I
> would think.  Instead prepare them in files in a directory (with
> format-patch -o $dir).  You can edit Cc: header in 0000-*.patch
> message while you proof-read what you are going to send out.

Thanks. Then I misinterpreted what --cc-cover actually means. All Cc:
lines have to be present in the cover letter already. Would be nice if
git would run a command like this to put the list into the coverletter:

 # git log --format=%b $base..$head | grep -iw ^cc: | sort -u

In the meantime I will remember to do that step manually.

Olaf

  reply	other threads:[~2015-03-23  8:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 17:35 cover letter and cc list Olaf Hering
2015-03-20 18:08 ` Junio C Hamano
2015-03-23  8:18   ` Olaf Hering [this message]
2016-02-26 12:35     ` Vineet Gupta

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=20150323081840.GB9332@aepfle.de \
    --to=olaf@aepfle.de \
    --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).