From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Marcos Paulo de Souza <mpdesouza@suse.com>
Cc: tools@linux.kernel.org
Subject: Re: [PATCH RESEND v4 0/3] livepatch: Move modules to selftests and add a new test
Date: Fri, 22 Dec 2023 15:31:58 -0500 [thread overview]
Message-ID: <20231222-neon-daring-grasshopper-fdc0c7@lemur> (raw)
In-Reply-To: <3a0b19b97cedd69b49a23aab35038e0844f3f1eb.camel@suse.com>
On Fri, Dec 22, 2023 at 04:13:40PM -0300, Marcos Paulo de Souza wrote:
> > How about the following:
> >
> > b4 send --only-to colleague1@example.com,colleague2@example.com
> >
> > This will automatically trigger the "don't tag and reroll" mode.
>
> Looks great! Exactly what I wanted to do, and very simple. Thanks a lot
> for looking into it!
I'm going to implement it as --dry-run-to, just to make it more obvious that
it's a dry-run action and won't trigger a tag-and-reroll.
So, you should be able to do:
b4 send --dry-run-to mentor1@example.com mentor2@example.com
The subject line prefixes will also include DRYRUN in that case, e.g.:
[PATCH DRYRUN 0/3] Some cover title
-K
bugbot assign to me
next prev parent reply other threads:[~2023-12-22 20:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 16:53 [PATCH RESEND v4 0/3] livepatch: Move modules to selftests and add a new test Marcos Paulo de Souza
2023-12-20 16:53 ` [PATCH RESEND v4 1/3] kselftests: lib.mk: Add TEST_GEN_MODS_DIR variable Marcos Paulo de Souza
2024-01-02 22:31 ` Joe Lawrence
2024-01-03 22:09 ` Shuah Khan
2024-01-08 17:13 ` Marcos Paulo de Souza
2024-01-09 19:31 ` Shuah Khan
2024-01-10 0:27 ` Marcos Paulo de Souza
2023-12-20 16:53 ` [PATCH RESEND v4 2/3] livepatch: Move tests from lib/livepatch to selftests/livepatch Marcos Paulo de Souza
2023-12-20 16:53 ` [PATCH RESEND v4 3/3] selftests: livepatch: Test livepatching a heavily called syscall Marcos Paulo de Souza
2023-12-21 12:17 ` [PATCH RESEND v4 0/3] livepatch: Move modules to selftests and add a new test Marcos Paulo de Souza
2023-12-21 20:10 ` Shuah Khan
2023-12-22 18:40 ` Konstantin Ryabitsev
2023-12-22 18:52 ` Marcos Paulo de Souza
2023-12-22 19:11 ` Konstantin Ryabitsev
2023-12-22 19:13 ` Marcos Paulo de Souza
2023-12-22 20:31 ` Konstantin Ryabitsev [this message]
2023-12-22 20:35 ` Kernel.org Bugbot
2023-12-22 20:40 ` b4: implement send --dry-run-to ADDR [ADDR ...] Kernel.org Bugbot
2023-12-22 20:35 ` livepatch: Move modules to selftests and add a new test Kernel.org Bugbot
2023-12-22 20:45 ` Kernel.org Bugbot
2024-01-03 20:15 ` [PATCH RESEND v4 0/3] " Joe Lawrence
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=20231222-neon-daring-grasshopper-fdc0c7@lemur \
--to=konstantin@linuxfoundation.org \
--cc=mpdesouza@suse.com \
--cc=tools@linux.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.