diff options
| author | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2020-03-18 18:06:10 -0400 |
|---|---|---|
| committer | Konstantin Ryabitsev <konstantin@linuxfoundation.org> | 2020-03-18 18:06:10 -0400 |
| commit | 8a0a359c76a25d74c3e2de6a350422ae9ca67798 (patch) | |
| tree | 30b9f66dbb64f3eba2ffa7f3afb24f011d5c6b7b /requirements.txt | |
| parent | be9d8fa6de85e317facd0839e5a67f918f95f21a (diff) | |
| download | b4-8a0a359c76a25d74c3e2de6a350422ae9ca67798.tar.gz | |
Handle vN that only exists in the cover letter
There are special cases where we have:
cover: [PATCH v3 00/NN] Foo
\- [PATCH 01/NN] Patch 1
- [PATCH 02/NN] Patch 2
While the submitter *should* be setting "v3" in all patches, it's not
uncommon to have that inferred from the cover letter. When cover letter
is properly upthread from the patch that has an inferred v1 revision, we
can check the revision on the cover letter and fix the patch revision to
match.
Reported-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Diffstat (limited to 'requirements.txt')
0 files changed, 0 insertions, 0 deletions