On Wed, 26 Jan 2005, Blaisorblade wrote:
So, I'd suggest to follow this policy to choose the work to merge:
- reduce *a lot* what is going to be merged... no new features, no code cleanups (especially NOT the Makefiles cleanups)...
- concentrate on stability... and on backing out the hostfs rewrite.
I am all for this. People wanting "new fetures" should be using the 2.6 tree + relevant patches anyway. 2.4 should focus only on stability, nothing else.
If there is users willing to have new features in 2.4 to the point that they provide these features backported to 2.4 then I am OK with having an "experimental" 2.4 patch with these aplied, but I do not think these belongs in the main 2.4 patch.
Regards Henrik
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
