Just my 2 cents. We just had this discussion for rdma-core and used this approach: https://github.com/linux-rdma/rdma-core/blob/master/Documentation/stable.md
There's a set of tools use by the kernel stable guys but I haven't gotten to them yet. https://git.kernel.org/pub/scm/linux/kernel/git/sashal/stable-tools.git/tree/ It handles both patch that need to be backported straightaway, or patch we later realize needed backporting. And even without the kernel tools, it is very easy to firlter out those patches within your mail client. Nicolas Le 28/11/2017 à 01:41, Hefty, Sean a écrit : > There are currently 2 stable branches actively being updated - 1.4.x and > 1.5.x. Up until this point, stable branches have resulted in limited > additional work -- at least to anyone other than me :). > > To assist with the process, I'd propose including a tag the signed-off-by > area to indicate if a patch should be cherry-picked. This is similar to the > linux-kernel method. For example: > > TAG: v1.5.x > Signed-off-by: Big Bird <[email protected]> > > or > > TAG: stable > Signed-off-by: Oscar <[email protected]> > > If we use this, we would need to select the 'TAG' (or just use 'TAG'), as > well as listing what values are possible (specific branches or general > stable). > > - Sean > _______________________________________________ > ofiwg mailing list > [email protected] > http://lists.openfabrics.org/mailman/listinfo/ofiwg _______________________________________________ ofiwg mailing list [email protected] http://lists.openfabrics.org/mailman/listinfo/ofiwg
