lkml.org 
[lkml]   [2018]   [Nov]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch 2/2] Documentation/process: Add tip tree handbook
On Thu, 8 Nov 2018, Greg KH wrote:
> On Thu, Nov 08, 2018 at 08:58:32PM +0100, Thomas Gleixner wrote:
> > Fixes: 1234567890AB ("subsys/comp: Short summary")
> > Backport-to: 4.14
>
> Ick, no. Just stick to the "Fixes:" tag. My scripts can now track when
> a patch is backported to a stable tree so that I know to apply it to
> older ones despite the original patch showing up in a newer release.

Fine with me.

I just did a few stats.

commits between 4.19-rc1 and 4.19-final:

Total commits: 2098

Total Cc: stable 334
Cc: stable 119 35%
Cc: stable #kver 10 3%
Cc: stable Revert 0 0%
Cc: stable Fixes 123 37%
Cc: stable Fixes #kver 81 24%

Total Fixes only 584
Fixes only > 4.18 227 39%
Fixes only <= 4.18 357 61%

and between 4.19 and todays top of tree:

Total commits: 12947

Total Cc: stable 251
Cc: stable 85 34%
Cc: stable #kver 28 11%
Cc: stable reverts 2 1%
Cc: stable Fixes 79 31%
Cc: stable Fixes #kver 55 22%

Total Fixes only 835
Fixes only > 4.19 830 99%
Fixes only <= 4.19 5 1%

Not much change in the 'cc stable' ratio for those without any information
and for those with Fixes tag and #kver.

The cc stable + kver and the cc stable + Fixes differ, but their sum is
roughly the same.

But the real interesting change is that between 4.19-rc1 and 4.19-final the
number of Fixes only (no CC stable) commits which fix a commit in 4.18 or
earlier is rather high, while the same category on post 4.19 is minimal.

I'll run a larger and more detailed scan to figure out whether there is a
trend or this is just random.

Thanks,

tglx


\
 
 \ /
  Last update: 2018-11-08 23:40    [W:0.083 / U:0.140 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site