All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter <p.repliesignored@rimuhosting.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
	user-mode-linux-devel@lists.sourceforge.net,
	user-mode-linux-user@lists.sourceforge.net
Subject: [uml-devel] Re: [uml-user] [POLL] Putting UML/2.4 into "fixes-only" mode
Date: Thu, 27 Jan 2005 12:55:32 +1300	[thread overview]
Message-ID: <41F82DF4.10506@rimuhosting.com> (raw)
In-Reply-To: <200501262310.49814.blaisorblade@yahoo.it>

+1

For my purposes I need solid, stable code.  I prefer a a 2.4 and 2.6 
kernel that builds without too many config gotchas.  And runs reliably. 
  e.g. right now I am using the blaisorblade 2.6.9-bs patches and the 
pre-hostfs 2.4 code.  That works well.

I'm all for different UML trees/patches that try out new features and 
make major changes.  And I will contribute to testing those if needed. 
But I would like to keep those patches/trees separate from the 'stable' one.

It is your time, and you can spend it how you like (obviously).  I'd be 
most happy if new work went into the 2.6 tree if that meant more would 
be done.  That seems to be where all new distros are going (not 2.4). 
And (give or take a bug or two) most of my UML instances run really well 
on the 2.6 tree.  If I had a really solid 2.6 kernel I don't think I'd 
even need the 2.4 one.

So if you can save some backporting efforts, work on adding more 2.6 
stability and new features (on the separate -mm type tree) that could be 
a win-win.

Cheers, Peter



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.


-------------------------------------------------------
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

  reply	other threads:[~2005-01-26 23:55 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 ` Peter [this message]
2005-01-27  2:22 ` [uml-devel] Re: [uml-user] " D. Bahi
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=41F82DF4.10506@rimuhosting.com \
    --to=p.repliesignored@rimuhosting.com \
    --cc=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    --cc=user-mode-linux-user@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.