All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@kernel.org
Subject: Re: b4 send: how to selectively suppress Cc?
Date: Wed, 14 Aug 2024 08:02:28 -0700	[thread overview]
Message-ID: <7hed6rno57.fsf@baylibre.com> (raw)
In-Reply-To: <20240813-tunneling-caped-piculet-e34d08@lemur>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:

> On Tue, Aug 13, 2024 at 03:58:10PM GMT, Kevin Hilman wrote:
>> How do I pursuade b4 send to selectively *not* send emails to some of
>> the emails it finds in to/from/sob etc?
>
> You should be able to accomplish this with b4.email-exclude:
>
>     A list of addresses to always exclude from the message recipients. Expects a
>     comma-separated list with shell-style globbing. E.g.:
>
>     email-exclude = *@codeaurora.org, *@obsolete.example.com
>
> Let me know if this doesn't work.

It works perfectly, thanks!

I guess I missed it because I didn't think to look at the `b4 ty` docs
for email settings while getting `b4 send` to work.  Maybe an item for
your TODO list is to add a pointer to those settings in the `b4 send`
doc?

Anyways, thanks for the tip and for the work on this really useful too.

Kevin

P.S. I just discovered the `b4 prep` feature of creating/tracking a
     branch from a sent series[1], and it's great!  Exactly what I
     needed for taking over a series from someone else.  Thanks!

[1] https://b4.docs.kernel.org/en/latest/contributor/prep.html#creating-a-branch-from-a-sent-series

      reply	other threads:[~2024-08-14 15:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13 22:58 b4 send: how to selectively suppress Cc? Kevin Hilman
2024-08-13 23:45 ` Konstantin Ryabitsev
2024-08-14 15:02   ` Kevin Hilman [this message]

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=7hed6rno57.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=tools@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.