Jeff, now we need actively to make sure everything we think is crucial is merged in 2.6.11 - release is approaching (after -rc2 only a handful of patches is being merged, and the announce says "Make sure I have everything"), so you should make sure to send Andrew anything needed on top of 2.6.11-rc2-bk3 (I say the -bk tree on purpose, because that's what becomes the real released tree) to make it compile.
Please make sure to tag the patches as "for merge before 2.6.11", otherwise we'll be in the 2.6.10 situation (20 patches to merge for 2.6.10, including the Bodo's fixes, merged just after 2.6.10). First of all making sure that things compile... also please try to be really conservative, a little error anywhere can hurt stability... Let's avoid this, PLEASE. I'm asking for this even because trying to maintain the -bb tree and to do some kind of Quality Assurance (i.e. especially answering to the various important discussions, which I do even to discover bugs not recognized by who saw them) is making impossible for me to do actual work... my development speed is slowing down too much. -- Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 http://www.user-mode-linux.org/~blaisorblade ------------------------------------------------------- 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-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
