On Fri, Sep 21, 2012 at 11:40:48AM -0400, Theodore Ts'o wrote: > Hi, > > I have a set of patches that are currently queued for merging for 3.6. > > I didn't mark them for [email protected], since they aren't a bug > fix, but rather a new feature. However, it occurs to me that this is a > feature that many enterprise/stable users would probably want. > > The patches are very low risk in that they only change the online > resizing codepath, and enable resizing for file systems that previously > would not support resizing. > > So what do you think? When these patches go upstream, should I send a > the commit id's or patches to [email protected]? And given that I > didn't mark them with a cc:[email protected], do I need to send > separate patches for each stable kernel, or just one for 3.5? I expect > they should apply cleanly all the way back to 3.2 or 3.0.
That sounds "nice", but it seems to be a feature, and doesn't meet the main requirements of the stable tree. However, odds are that distros based on the stable trees would love a solid patchset that adds this option. So post the patches and I bet the distros will pick it up from there, I know I'll go add them to the LTSI kernel, and that's used by others as well. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
