On 07/16/2012 01:11 PM, Willy Tarreau wrote:
Hi John,
On Mon, Jul 16, 2012 at 12:09:43PM -0700, John Stultz wrote:
On 07/16/2012 12:04 PM, Greg Kroah-Hartman wrote:
Or is it better to roll a series of upstream commits into one
-stable commit so reviewers can see it is correct, without slogging
through a series?
Nope, series is best, if at all possible.
But, if things are messier for older kernel releases, then it might make
sense to do a smaller number of patches, only if it is still readable
and makes sense to do so.
Sounds good. I'll start spinning them up then.
For 2.6.32, I'm used to backport 3.0 material and sometimes to ask for
some help when I feel uneasy. There are a few things in the queue now
and I intend to make a new release "soon". I can happily wait for the
leapsecond fixes to be merged into other stable branches first. If you
think the backport should be easy, don't waste your time with it, at
worst I'll ping you if I can't do it. Otherwise if you think it's easy
only for you, then your patches would be much appreciated, so it's up
to you :-)
I don't expect them to be trivial. So I was hoping to focus on doing
them the first half of this week (assuming nothing else goes awry upstream).
That said, if you want to take a swing at backporting the 3.2.x changes
(which I'm working on now) to 2.6.32.x once I've sent those out, it
might be good just so we can compare notes and have more eyes on the
details.
thanks
-john
--
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
