From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: bugzilla-daemon@gentoo.org
Subject: Re: [uml-devel] [Bug 49277] Compile of usermode-sources-2.6.x fails
Date: Wed, 9 Feb 2005 22:40:44 -0500 [thread overview]
Message-ID: <200502092240.44915.rob@landley.net> (raw)
In-Reply-To: <E1Cytuz-0002nD-OP@nuthatch.gentoo.org>
On Wednesday 09 February 2005 10:38 am, bugzilla-daemon@gentoo.org wrote:
> ------- Additional Comments From dsd@gentoo.org 2005-02-09 07:38 PST
> ------- Could someone please update me with the status of this bug? Are
> there still problems?
>
> I notice that the latest version in portage is based on 2.6.8.1. Would
> upgrading to a newer version (assuming there are newer releases) help at
> all?
I believe it was fixed in 2.6.11-rc3-bk2 or thereabouts, but I personally
would prefer to hold off closing it until 2.6.11 actually ships. The UML in
2.6.10 didn't build, 2.6.9 was unusable out of the box, and 2.6.11-rc3
introduced _new_ build breakage on top of what -rc2 had because Linus just
doesn't test it.
If the UML in 2.6.11-final works, consider the bug resolved.
Rob
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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
next prev parent reply other threads:[~2005-02-10 4:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 15:38 [uml-devel] [Bug 49277] Compile of usermode-sources-2.6.x fails bugzilla-daemon
2005-02-10 3:40 ` Rob Landley [this message]
2005-02-10 11:31 ` Blaisorblade
2005-02-10 14:16 ` Rob Landley
2005-02-10 15:44 ` Blaisorblade
2005-02-11 0:31 ` Rob Landley
2005-02-11 2:33 ` Blaisorblade
2005-02-11 2:42 ` Rob Landley
2005-02-11 3:48 ` Blaisorblade
[not found] <bug-49277@bugs.gentoo.org>
2005-06-07 0:57 ` bugzilla-daemon
2005-06-07 14:31 ` Nix
2005-06-07 14:52 ` Blaisorblade
2005-06-07 15:54 ` Nix
2005-06-07 16:11 ` Blaisorblade
2005-06-07 16:21 ` Nix
2005-06-07 16:44 ` Blaisorblade
2005-06-07 19:47 ` Nix
2005-06-08 0:34 ` Blaisorblade
2005-06-08 17:38 ` Nix
2005-06-08 18:10 ` Blaisorblade
2005-06-09 22:08 ` Blaisorblade
2005-06-07 16:52 ` Blaisorblade
2005-06-07 16:02 ` Nix
2005-07-06 9:57 ` bugzilla-daemon
2005-07-06 16:22 ` bugzilla-daemon
2005-07-09 22:41 ` bugzilla-daemon
2005-07-12 17:13 ` bugzilla-daemon
2005-07-13 15:14 ` bugzilla-daemon
2005-07-14 8:11 ` bugzilla-daemon
2005-07-14 19:57 ` Rob Landley
2005-07-14 20:22 ` Rob Landley
2005-07-14 8:12 ` bugzilla-daemon
2005-07-14 8:39 ` bugzilla-daemon
2005-07-14 8:40 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2005-05-08 11:55 bugzilla-daemon
2005-04-30 0:41 bugzilla-daemon
2005-04-28 16:26 bugzilla-daemon
2005-04-13 15:50 bugzilla-daemon
2005-04-08 18:01 bugzilla-daemon
2005-03-19 20:54 bugzilla-daemon
2005-03-02 23:28 bugzilla-daemon
2005-03-02 15:04 bugzilla-daemon
2005-02-18 13:05 bugzilla-daemon
2005-02-09 21:58 bugzilla-daemon
2005-01-12 1:24 bugzilla-daemon
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=200502092240.44915.rob@landley.net \
--to=rob@landley.net \
--cc=bugzilla-daemon@gentoo.org \
--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.