ez: introduce --in-reply-to for send #60
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When sending numerous patchsets touching multiple projects, the structure of the email thread could be top-level cover letter with patchsets as subthreads (replies). As an example, while developing a filesystem feature one can also develop tests for xfstests for that feature.
With --in-reply-to one can send top-level cover and use it as base for sending other b4 managed branches.
This patch introduces 'b4 --in-reply-to IDENTIFIER' for adding 'In-Reply-To:' header to cover-letter message.