On Mon, May 3, 2010 at 2:26 PM, Zack Rusin <za...@vmware.com> wrote: > On Monday 03 May 2010 14:17:30 Alex Deucher wrote: >> On Mon, May 3, 2010 at 2:09 PM, Brian Paul <bri...@vmware.com> wrote: >> > I think it's worth exploring a policy of somehow tagging commits as >> > candidates for back-porting to the stable branch so they can be some >> > level of accounting and tracking. I don't think we need to work that out >> > immediately though. >> >> On this point, it might be useful to update a cherry-pick wiki when >> you do cherry-pick commits back to the stable branch. That way when >> it comes time for the next stable point release, we can refer to the >> list to update the release notes (or even link to the page from the >> release notes for finer grained details). Thoughts? > > Would that actually gain us anything? I mean what would be the difference > between that list and "git log last_stable_releast..current_stable_branch" ? > I think what Brian meant was adding a magic tag to the commit message, e.g. > "BACKPORT", or "FIX" which I could make the Mesa3D commit hook pick out from > the commits and either create a bugzilla entry for that commit, email the > author after some time, add that commit sha1 hash to some list or do some > other random action. But as Brian mentioned this is something we don't have to > figure out right away but see what would actually be useful as folks start > cherry picking to the stable branch.
I guess it's just more of a manual variant of the same thing. Maybe we can add a mesa-stable address and you can add a cc in the commit like the kernel does. Alex _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
