On 15/8/22 14:25, Thomas Reim wrote:
In order to make review easier for you a subsequent mail will outline
the proposed changed to the provided patch (patch-for-patch format).
I fear this process will get confusing.
What is mostly done by people for patch updates during review is to
post the entire series with a v<n>, for this patch would be [PATCH v2
3/4],
and then in the cover letter (or the patch itself if there's only one) a
simple summary added to describe the changes.
Like:
- changes for v2:
- short description of change.
If that doesn't fit well with your workflow I can deal with the
patch-for-patch process.
Ian
Shame on me. I could have checked your procedure beforehand.
v2 has been sent.
That sort of process is pretty widely used by community projects.
Especially those that have a lot of contributors, its so easy to
become confused without some way to identify patch revisions of
emails.
Ian
