Urgent queue
cover Urgent queue
Two patches that are small bugfixes / features that are what I consider the immediately merge queue.
Quoted 2 lines · Christoph Hellwig
Two patches that are small bugfixes / features that are what I consider the immediately merge queue.
The entire set of 30 patches has passed XFSQA on my test box....
Cheers,
Dave.
Signature · 2 lines
Dave Chinner [email protected]
Quoted 5 lines · Dave Chinner
Quoted 2 lines · Christoph Hellwig
Two patches that are small bugfixes / features that are what I consider the immediately merge queue.
The entire set of 30 patches has passed XFSQA on my test box....
individually (by series) or only after all 30? Bisectability is important, as Christoph alluded to in another thread. Is the intention to try and take this lot for 28-rc3? I think Lachlan is now very close to a pull req for .28, depending on his testing for the memleak and deadlock fixes - time is now getting pretty short :)
Cheers
-- Mark
Quoted 5 lines · Mark Goodwin
individually (by series) or only after all 30? Bisectability is important, as Christoph alluded to in another thread. Is the intention to try and take this lot for 28-rc3? I think Lachlan is now very close to a pull req for .28, depending on his testing for the memleak and deadlock fixes - time is now getting pretty short :)
Even urgent isn't urgent enough for the first 2.6.28 series, please get that one out ASAP, I don't want to miss it. The two patches from the urgent queue are something I would consider for a second .28 pull, everything else is .29 material.
But it would be highly useful if we could open up a .29 staging tree that can be QAed and included in linux-next ASAP..
Quoted 11 lines · Mark Goodwin
Quoted 5 lines · Dave Chinner
Quoted 2 lines · Christoph Hellwig
Two patches that are small bugfixes / features that are what I consider the immediately merge queue.
The entire set of 30 patches has passed XFSQA on my test box....
individually (by series) or only after all 30? Bisectability is important, as Christoph alluded to in another thread.
All - there is no way in hell I'm going to run qa on each patch individually given that most of them are trivial.
Bisectability is mainly about ensuring each patch builds independently and at least runs without obvious problems. Given most of the patches were independent, running QA over the end series is usually sufficient to check that they will run sufficiently well to do a bisect if they build.
That being said, given that I *have bisected* that series (to find the directory corruption problem as a result of upgrading the underlying kernel), I'd say it's just fine.
Quoted 2 lines
Is the intention to try and take
this lot for 28-rc3?
Just the urgent ones, I think. The rest are 2.6.29 candidates but they still should be checked in and merged into the master branch so that we can test them well before the .29 merge window comes around...
Quoted 3 lines
I think Lachlan is now very close to a pull req for
.28, depending on his testing for the memleak and deadlock fixes - time is now getting pretty short :)
Given that 2.6.28-rc3 is now out, I have serious doubts that Linus will take an update of this size. We've missed the merge window by two weeks....
Cheers,
Dave.
Signature · 2 lines
Dave Chinner [email protected]