From: Daniel Mack <zonque@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: git@vger.kernel.org
Subject: Re: Suppressing auto-cc for specific addresses
Date: Mon, 8 Aug 2011 09:24:02 +0200 [thread overview]
Message-ID: <CACTFLAOhApGVNZ7JsWhoHBEaQ_87stXjxkXvadmauNfhSuPD1g@mail.gmail.com> (raw)
In-Reply-To: <20110807234634.GA3236@kroah.com>
On Mon, Aug 8, 2011 at 1:46 AM, Greg KH <greg@kroah.com> wrote:
> On Sun, Aug 07, 2011 at 10:20:26PM +0200, Daniel Mack wrote:
>> I'm looking for a way to suppress certain Cc: fields that are
>> normally automatically added for addresses mentioned in Cc: lines
>> found in patches.
>>
>> In particular, the kernel rules for marking patches for stable
>> release inclusion wants users to add a "Cc: stable@kernel.org" line
>> in the patch itself but to not actually send a copy of that patch to
>> that address. It will be picked automatically once the patch was
>> applied upstream.
>
> There is no "rule" that says you can not send a copy of the patch to
> stable@kernel.org, in fact that happens a lot and is fine and I have no
> problem with that at all.
Ok, thanks for explaining. In fact, I've done it that way ever since,
and never thought that there is any problem with it. But the topic
came up lately on the ALSA ML (and was continued off-list later), and
reading Documentation/stable_kernel_rules.txt again, I became aware of
the fact that sending it to stable@ is not actually necessary (while
at the same time, it doesn't seem to be frowned upon).
Anyway, I found it strange not have a way in git to achive this, and
maybe this new feature has other uses, too?
Thanks,
Daniel
next prev parent reply other threads:[~2011-08-08 7:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 20:20 Suppressing auto-cc for specific addresses Daniel Mack
2011-08-07 23:46 ` Greg KH
2011-08-08 7:24 ` Daniel Mack [this message]
[not found] ` <D95ADFD4-2504-4BE6-BCD4-7B916F6F2FEB@gmail.com>
2011-08-08 10:58 ` Daniel Mack
2011-08-08 20:44 ` Jeff King
2011-08-08 21:01 ` Daniel Mack
2011-08-08 21:11 ` Greg KH
2011-08-08 21:07 ` Jonathan Nieder
2011-08-09 7:01 ` Jeff King
2011-08-09 7:40 ` Daniel Mack
2011-08-08 21:17 ` Jonathan Nieder
2011-08-09 1:41 ` 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=CACTFLAOhApGVNZ7JsWhoHBEaQ_87stXjxkXvadmauNfhSuPD1g@mail.gmail.com \
--to=zonque@gmail.com \
--cc=git@vger.kernel.org \
--cc=greg@kroah.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).