-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
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>
- Loading branch information
Showing
4 changed files
with
74 additions
and
36 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hello, first thanks a lot for this contribution which makes total sense!
I however find this prefix a bit misleading, "dry run" really means "nothing sent". I understand the idea of saying "we don't send upstream" but it kind of deviates too much from the original Git term IMHO, so I would really prefer another prefix. "INTERNAL" or "REVIEW" or "DOWNSTREAM" maybe?