On 2012-01-22 20:07:32 +0100, Reinhard Tartler wrote: > On Sun, Jan 22, 2012 at 7:29 PM, Janne Grunau <[email protected]> wrote: > > Hi, > > > > I was thinking how we could make tracking bugfixes for release branches > > easier. I see nothing fundamentally wrong with the Linux stable tree > > workflow. It is as most linux kernel things email based and works by > > adding a 'CC: [email protected]' line to the commit message. > > > > The email address should be in our case either a mailing list tracked by > > patchwork or a email address which feeds patches into patchwork. The > > commit hook of the git server will CC that address on the commit > > notification message. If the CC:-line was forgotten the commit email > > can still be bounced later to the address. > > I'd very much welcome such a mailing list. Additionally, I'd also like > to use it for general coordination of stable releases. > > > > > Patchwork is unfortunately not an ideal fit for this purpose. The post > > commit hook will mark patches as committed when they are pushed to > > a single release branch although they might need to go into more than > > one branch. Or it will miss it completely when the backport changed > > the commit too much. > > Even if we can't use patchwork as tracker, it is still useful for > archiving and viewing old bugs. > > > > > While this is far from a perfect solution it is imho a worthwhile > > improvement over the current situation. > > Indeed!
Mailinglist created and patchwork tracking enabled: https://lists.libav.org/mailman/listinfo/libav-stable http://patches.libav.org/project/libav-stable/list/ Janne _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
