* [uml-devel] UML merge in after 2.6.8.1 - what to do now
@ 2004-08-30 19:40 BlaisorBlade
2004-09-07 21:49 ` [uml-devel] " Jeff Dike
0 siblings, 1 reply; 2+ messages in thread
From: BlaisorBlade @ 2004-08-30 19:40 UTC (permalink / raw)
To: Jeff Dike; +Cc: user-mode-linux-devel
I've just seen in my mailbox the mails from Andrew Morton to Linus Torvalds,
which contain the UML merge - 2.6.9-rc1-mm1 already lists them as merged, as
you can check here: http://kerneltrap.org/node/view/3720
Now, how will we work? I have some ideas about this, which I'd like to discuss
with everybody here. I think that the UML patch will become the "development
tree" of UML, where new patches hang around to get some testing, while the
mainline kernel should get only safe patches. For instance, for now the humfs
and filehandle work must *not* go in mainline, since they are highly
experimental.
Also, the various uml patch should never be actually "merged" inside the UML
patch: it must always be a patchset, i.e. a collection of separate patches.
Like -mm. So merging with mainline will be easier, as reviewing separate
patches or dropping bad ones.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply [flat|nested] 2+ messages in thread
* [uml-devel] Re: UML merge in after 2.6.8.1 - what to do now
2004-08-30 19:40 [uml-devel] UML merge in after 2.6.8.1 - what to do now BlaisorBlade
@ 2004-09-07 21:49 ` Jeff Dike
0 siblings, 0 replies; 2+ messages in thread
From: Jeff Dike @ 2004-09-07 21:49 UTC (permalink / raw)
To: BlaisorBlade; +Cc: Jeff Dike, user-mode-linux-devel
blaisorblade_spam@yahoo.it said:
> Now, how will we work? I have some ideas about this, which I'd like to
> discuss with everybody here. I think that the UML patch will become
> the "development tree" of UML, where new patches hang around to get
> some testing, while the mainline kernel should get only safe patches.
> For instance, for now the humfs and filehandle work must *not* go in
> mainline, since they are highly experimental.
Yeah, this sounds reasonable. My tree will be experimental stuff, and
forwarded to Andrew/Linus when it is considered OK.
> Also, the various uml patch should never be actually "merged" inside
> the UML patch: it must always be a patchset, i.e. a collection of
> separate patches. Like -mm. So merging with mainline will be easier,
> as reviewing separate patches or dropping bad ones.
Yup.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-09-07 20:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-08-30 19:40 [uml-devel] UML merge in after 2.6.8.1 - what to do now BlaisorBlade
2004-09-07 21:49 ` [uml-devel] " Jeff Dike
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox