From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] send-email: Add an option to suppress adding a specific email address
Date: Thu, 23 May 2019 02:48:38 +0200 [thread overview]
Message-ID: <87y32yt2qh.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <87d0kaj98f.fsf@xmission.com>
On Thu, May 23 2019, Eric W. Biederman wrote:
> Make it easy to suppress stable@vger.kernel.org. Long story short it
> is desirable to have ``Cc: stable@vger.kernel.org'' on many bug fixes
> sent to the linux kernel. It is not always desirable to actually the
> stable maintainer immediately as the patches are still being reviewed
> etc. Actually cc'd the stable maintainers in the linux kernel is not
> even really necessary as they will always find the tag after the patch
> has been merged in the commit body.
>
> So I am adding yet another suppress command "suppress-addr" that will
> take an email address keep that email address from being automatically
> added to a destination the email will be sent to.
I have a rewrite of much of the adjacent code queued in "next", can you
check if applying it to that branch makes this work as you expect?
Whether it does or not, this change should have a corresponding test
update to t/t9001-send-email.sh, so we can just run that to see if it's
doing the right thing.
next prev parent reply other threads:[~2019-05-23 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 0:38 [PATCH] send-email: Add an option to suppress adding a specific email address Eric W. Biederman
2019-05-23 0:48 ` Ævar Arnfjörð Bjarmason [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-23 0:32 Eric W. Biederman
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y32yt2qh.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=ebiederm@xmission.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).