diff options
| author | Stephen Finucane <stephen@that.guru> | 2020-03-04 15:48:56 +0000 |
|---|---|---|
| committer | Stephen Finucane <stephen@that.guru> | 2020-03-11 10:10:50 +0000 |
| commit | d6ee204ef516643e62bcf27692dddf83e1042f5f (patch) | |
| tree | acef20aa0203775706507bf1de4779b3da7c9fef /releasenotes/notes | |
| parent | b8a1673e356f2ad49f83eff82262b8d3c066f2fd (diff) | |
| download | patchwork-d6ee204ef516643e62bcf27692dddf83e1042f5f.tar patchwork-d6ee204ef516643e62bcf27692dddf83e1042f5f.tar.gz | |
parser: Don't group patches with different versions in a series
As noted in #340 [1], if a patch from a series is dropped or
miscategorised, patches from a later revision of that series can end up
included in the earlier series rather than in their own series. This was
actually intentional as part of the fix for #105 [2]. However,
completely ignoring this information can be problematic. Refine things
by checking for versions and, if they don't match, using timeboxing to
try guess if they should be kept together. This would resolve the issue
seen in #340 while preventing a regression for #105.
[1] https://github.com/getpatchwork/patchwork/issues/340
[1] https://github.com/getpatchwork/patchwork/issues/105
Signed-off-by: Stephen Finucane <stephen@that.guru>
Tested-by: Ali Alnubani <alialnu@mellanox.com>
Related: #340
Related: #105
Diffstat (limited to 'releasenotes/notes')
| -rw-r--r-- | releasenotes/notes/issue-340-45deefed937b2090.yaml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/releasenotes/notes/issue-340-45deefed937b2090.yaml b/releasenotes/notes/issue-340-45deefed937b2090.yaml new file mode 100644 index 0000000..150264a --- /dev/null +++ b/releasenotes/notes/issue-340-45deefed937b2090.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - | + A bug that would result in patches from later series revisions being + included in earlier revisions has been resolved. |