03/02/2020 16:59, Kevin Traynor: > During backporting, if the fixes or stable tag are missing, > it usually requires some investigation by stable maintainer > as to why. > > The presence of a fixes tag may be known from whether the > originating release of the issue is printed at the end of the > line but with variable line lengths and nested partial fixes > it doesn't catch the eye. > > When there are a large amount of commits, adding an aligned column > indicating the presence of a fixes tag beside the stable one makes > it easier to quickly see the patches requiring further investigation. > > e.g. > 20.02 8f33cbcfa S F net/i40e/base: fix buffer address (16.04) > 20.02 4b3da9415 S F net/i40e/base: fix error message (1.7.0) > 20.02 1da546c39 - F net/i40e/base: fix missing link modes (17.08) > 20.02 79bfe7808 S F net/i40e/base: fix Tx descriptors number (1.7.0) > 20.02 50126939c - F net/i40e/base: fix retrying logic (18.02) > 20.02 dcd05da0a S F app/testpmd: fix GENEVE flow item (18.02) > 20.02 b0b9fdad2 S - net/bnx2x: support secondary process (N/A) > 20.02 f8279f47d S F net/netvsc: fix crash in secondary process (18.08) > > Signed-off-by: Kevin Traynor <ktray...@redhat.com>
Looks nice. Applied, thanks
