Re: Suppressing auto-cc for specific addresses

From: Daniel Mack <zonque@gmail.com>
Date: Aug 8, 2011, 07:24 UTC
Message-ID: <CACTFLAOhApGVNZ7JsWhoHBEaQ_87stXjxkXvadmauNfhSuPD1g@mail.gmail.com>
In-Reply-To: <20110807234634.GA3236@kroah.com>

On Mon, Aug 8, 2011 at 1:46 AM, Greg KH <greg@kroah.com> wrote:

Show 14 quoted lines

> 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