From: Jeff Dike <jdike@karaya.com>
To: linux-kernel@vger.kernel.org, user-mode-linux-user@lists.sourceforge.net
Subject: [ANNOUNCE] UML 2.5.26
Date: Wed, 17 Jul 2002 16:17:56 -0500 [thread overview]
Message-ID: <200207172117.QAA03530@ccure.karaya.com> (raw)
After a long, relaxing period of ignoring 2.5, I decided that it was about
to catch up. So, UML 2.5.26 is available. It is the same code as the current
UML - 2.4.18-40.
This went through my testing without major problems. However, it was a quick
merge (I started on Thursday with 2.5.3-pre5 and finished on Monday with
2.5.25), so there may be lurking problems.
Any problems should be reported to the uml-devel list
(user-mode-linux-user at lists dot sourceforge dot net).
At some point in the near future, I am going to split this up a bit and
send it to Linus.
The patch is available at
http://uml-pub.ists.dartmouth.edu/uml/uml-patch-2.5.26-1.bz2
For the other UML mirrors and other downloads, see
http://user-mode-linux.sourceforge.net/dl-sf.html
Other links of interest:
The UML project home page : http://user-mode-linux.sourceforge.net
The UML Community site : http://usermodelinux.org
Jeff
reply other threads:[~2002-07-17 20:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200207172117.QAA03530@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--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.