From: Jeff Dike <jdike@addtoit.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: UML merge in after 2.6.8.1 - what to do now
Date: Tue, 07 Sep 2004 17:49:26 -0400 [thread overview]
Message-ID: <200409072149.i87LnQBP010747@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Mon, 30 Aug 2004 21:40:15 +0200." <200408302140.15460.blaisorblade_spam@yahoo.it>
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
prev parent reply other threads:[~2004-09-07 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200409072149.i87LnQBP010747@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox