From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Recommended "head" branch?
Date: Sun, 16 Jan 2005 12:38:54 -0500 [thread overview]
Message-ID: <200501161238.54374.rob@landley.net> (raw)
I'm under the impression blaisorblade isn't going to continue his "stable"
tree now that patches are flowing easily into main, but the hang I'm seeing
in 2.6.9-bb persists (I tried mem=64M but that didn't help either). Probably
something small and simple to fix, but I haven't tracked it down yet...
I can't get 2.6.11-rc1 ARCH=um to compile. (Fixed the first build break to
receive a more elaborate one shortly thereafter, which is not a good sign...)
Is there a recommended tree I should be looking at?
Rob
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2005-01-16 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 17:38 Rob Landley [this message]
2005-01-17 4:00 ` [uml-devel] Recommended "head" branch? Jeff Dike
2005-01-17 2:29 ` Frank Sorenson
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=200501161238.54374.rob@landley.net \
--to=rob@landley.net \
--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.