[Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process

Steven Rostedt rostedt at goodmis.org
Wed Jul 31 02:20:40 UTC 2013


On Mon, 2013-07-29 at 13:58 -0400, Paul Gortmaker wrote:

> No. Won't work.  You'd be asking the maintainer to put the commit on
> the lowest common denominator for all stable releases.  And then be
> asking Linus to pull little fragmented branches with v2.6.32 as their
> baseline commit -- pushing the work of a "forward port" onto the hands

Egad! I'm just imagining the horror that would do to a git bisect!

-- Steve

> of the person doing the merge.  Plus we generally want the commit to
> look roughly applicable to the rc1 release it is merged into, which
> means the backporting work (if any) has to land on the person wanting
> to do the stable backport.  And if the backport is non-trivial, then
> that is a darn good sign that they seriously might want to consider
> the applicability of that commit to the old release.  It was one of
> the metrics that I sure considered.




More information about the Ksummit-2013-discuss mailing list