From: Dominik Brodowski <linux@dominikbrodowski.net>
To: gitster@pobox.com
Cc: Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
git@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: git send-email and sending the cover-letter to all cc addresses found in a patch series
Date: Fri, 23 Mar 2018 08:38:58 +0100 [thread overview]
Message-ID: <20180323073858.GA12077@light.dominikbrodowski.net> (raw)
In-Reply-To: <CA+55aFwM8mMyZZ9wH2ExAkTKg9Mwie1hOtXz87ivi0nhsZ49Ug@mail.gmail.com>
On Thu, Mar 22, 2018 at 10:44:54AM -0700, Linus Torvalds wrote:
> On Thu, Mar 22, 2018 at 10:29 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > But why !? Either Cc me on more of the series such that the whole makes
> > sense, or better yet, write a proper Changelog.
>
> This is a common issue. We should encourage people to always send at
> least the cover-page to everybody who gets cc'd, even if they don't
> get the whole series.
Will try to do that in future. Does git send-email have such an option? Or
do I have to specify all cc addresses in the cover letter manually? I found
some reference to an unresolved discussion on git@ of that topic in 2016, so
I might not be the only one who could make use of that feature...
Thanks,
Dominik
next parent reply other threads:[~2018-03-23 7:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180322090059.19361-1-linux@dominikbrodowski.net>
[not found] ` <20180322090059.19361-24-linux@dominikbrodowski.net>
[not found] ` <20180322172959.GX4043@hirez.programming.kicks-ass.net>
[not found] ` <CA+55aFwM8mMyZZ9wH2ExAkTKg9Mwie1hOtXz87ivi0nhsZ49Ug@mail.gmail.com>
2018-03-23 7:38 ` Dominik Brodowski [this message]
2018-03-23 7:49 ` git send-email and sending the cover-letter to all cc addresses found in a patch series Joe Perches
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=20180323073858.GA12077@light.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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).