From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: mpdesouza@suse.com, konstantin@linuxfoundation.org,
tools@linux.kernel.org
Subject: Re: b4: implement send --dry-run-to ADDR [ADDR ...]
Date: Fri, 22 Dec 2023 20:40:31 +0000 (UTC) [thread overview]
Message-ID: <20231222-b218302c5-d6e268c23183@bugzilla.kernel.org> (raw)
In-Reply-To: <20231222-horned-caiman-of-freedom-3fec0a@lemur>
Konstantin Ryabitsev writes in commit 4e03211130d5afbf26297bee8b549013fc30e6fc:
ez: implement send --dry-run-to
Sometimes it is useful to be able to send the series out to someone for
a quick one-over review (e.g. to your mentor, boss, colleague) before
actually sending it out to the actual maintainers.
It is now possible to do so with:
b4 send --dry-run-to addr@example.com
This will not trigger a tag-and-reroll and will include a DRYRUN into
the patch prefixes to clearly indicate that it's not the final
submission that should be used for review.
Suggested-by: Marcos Paulo de Souza <mpdesouza@suse.com>
Link: https://lore.kernel.org/f5c38763b4d42cfafdaac24d83ec18b81dfc073a.camel@suse.com
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=218302
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
(via https://git.kernel.org/pub/scm/utils/b4/b4.git/commit/?id=4e03211130d5)
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
prev parent reply other threads:[~2023-12-22 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231220-send-lp-kselftests-v4-0-3458ec1b1a38@suse.com>
[not found] ` <55b717dba239f3bedf0da7e25925e390a63459f5.camel@suse.com>
2023-12-22 18:40 ` [PATCH RESEND v4 0/3] livepatch: Move modules to selftests and add a new test 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
2023-12-22 20:35 ` Kernel.org Bugbot
2023-12-22 20:40 ` Kernel.org Bugbot [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=20231222-b218302c5-d6e268c23183@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=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 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).