From: "D. Bahi" <dbahi@enterasys.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [uml-user] [POLL] Putting UML/2.4 into "fixes-only" mode
Date: Wed, 26 Jan 2005 21:22:16 -0500 [thread overview]
Message-ID: <41F85058.8050106@enterasys.com> (raw)
In-Reply-To: <200501262310.49814.blaisorblade@yahoo.it>
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
I would like a 2.4 that is stable. with a working hostfs.
(that i can run valgrind against - heh, not umls fault here.)
Also, the uml web site needs to be authoritative. building
the above should not require patching from additional
sources announced on the list.
That said, 2.4 and 2.6 are both 'stable' kernel branches
that have had quite a bit of UML development in them. So,
if it helps future maintaining of both 2.4 and 2.6, at
least until 2.7 appears, then do what you need to do.
please don't abandon 2.4 until 2.7 is well under way.
Maybe you could break up the 2.4 patches into 'stable'
'testing' and 'experimental' ?
db
Blaisorblade wrote:
>Jeff, I've seen the beginning of your work on back-porting all the patches
>from 2.6 to 2.4...
>
>It's a huge work, but what is more important, it could obviously hurt
>stability...
>
>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.
>
>
--
db
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2005-01-27 2:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 22:10 [uml-devel] [POLL] Putting UML/2.4 into "fixes-only" mode Blaisorblade
2005-01-26 23:55 ` [uml-devel] Re: [uml-user] " Peter
2005-01-27 2:22 ` D. Bahi [this message]
2005-01-28 15:46 ` Blaisorblade
2005-01-29 5:39 ` [uml-devel] " Jeff Dike
2005-02-04 5:54 ` Blaisorblade
2005-01-30 13:28 ` [uml-devel] " Henrik Nordstrom
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=41F85058.8050106@enterasys.com \
--to=dbahi@enterasys.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.