From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] uml-patch-2.6.3-rc2-1
Date: Sun, 15 Feb 2004 12:56:41 +0100 [thread overview]
Message-ID: <200402151256.41707.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200402131818.i1DIIRsq002831@ccure.user-mode-linux.org>
Alle 19:18, venerdì 13 febbraio 2004, Jeff Dike ha scritto:
> This patch updates UML to 2.6.3-rc2. This breaks with my usual practice of
> ignoring test patches. However, when I updated my UML tree, I had
> forgotten that my stock Linus tree was up to 2.6.3-rc2. I took this as a
> sign from a higher power that this was Meant To Be.
You seem too serious about your maintainer role! You have started writing
announces in The Way Linus Torvalds Does It (tm) :-) !
However, in my opinion what this higher power wants is that you post this
(with the needed changes) to Andrew Morton and that he includes it in 2.6.3!
And dropping the tty-uml-something piece.
> As well as catching up, there are some bug fixes and cleanups -
> modules should now work
About the R_386_* macros needed for this, they are defined twice in the patch
(archparam-i386.h and elf.h; they should be for now in elf.h, and in the
future in elf-i386.h since they are architecture-specific).
> worked around a process start time bug
> fixed a bug which caused ps to divide by zero
>
> The 2.6.3-rc2-1 UML patch is available at
> http://www.user-mode-linux.org/mirror/uml-patch-2.6.3-rc2-1.bz2
>
> BK users can pull my 2.5 repository from
> http://www.user-mode-linux.org:5000/uml-2.5
About this, I have a doubt: do you upload only the releases there (as in 2.4's
cvs) or also the single changesets? You could do the second by tagging the
releases (I don't use BitKeeper, but CVS allows it, and BitKeeper is by far
more sophisticated), so that users can use the stable version. Waiting for
new features to get little bugfixes (the long long host_hz, for instance)
sometimes is tiring. And not knowing what is in the repository and what was
merged (sometimes mails are confusing).
Also, you could probably ask Andrew Morton to upgrade from your repository for
mm patches, as he does for various other BitKeeper trees (he said "just ask
for this special treatment"); you would only need to drop even from the stock
patch the /proc/mm support for nested UML's (which is not at all a bad thing,
since it's not used heavily while nested UML would need testing).
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&opÌk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-02-15 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 18:18 [uml-devel] uml-patch-2.6.3-rc2-1 Jeff Dike
2004-02-13 18:38 ` Matt Ayres
2004-02-13 23:58 ` Nicholas Lee
2004-02-15 11:56 ` BlaisorBlade [this message]
2004-02-15 16:21 ` Thomas Schwinge
2004-02-19 20:13 ` [uml-devel] uml-patch-2.6.3-rc2-1 Sven Köhler
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=200402151256.41707.blaisorblade_spam@yahoo.it \
--to=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