From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: xen-devel@lists.xensource.com
Subject: Re: [ANNOUNCE] Tree freeze for 3.2.0
Date: Wed, 07 Nov 2007 13:49:20 +0100 [thread overview]
Message-ID: <4731B450.7000503@inria.fr> (raw)
In-Reply-To: <C35758E8.1808F%keir.fraser@eu.citrix.com>
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
Keir Fraser a écrit :
> Unsurprisingly given the recent churn rate, the tree isn't in a particularly
> stable state right now. I will push the staging tree into the main public
> tree later today, to encourage wider testing and fixing. Let's aim for a
> strong .0 release!
May I ask then this patch I already submitted twice get included ?
Basically, the original network-bridge scripts assume interface is the
last element on on the ouput line, whereas it is not always true,
especially if you use routing metrics.
--
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62
[-- Attachment #2: xen-unstable-network-bridge.patch --]
[-- Type: text/x-patch, Size: 529 bytes --]
Signed-off-by: Guillaume Rousse <Guillaume.Rousse@inria.fr>
--- network-bridge 2007-11-07 13:46:30.000000000 +0100
+++ network-bridge~ 2007-11-07 13:37:55.000000000 +0100
@@ -72,8 +72,8 @@
echo "$ifs"
}
-netdev=${netdev:-$(ip route list 0.0.0.0/0 | \
- sed 's/.*dev \([a-z]\+[0-9]\+\).*$/\1/')}
+netdev=${netdev:-$(ip route list | awk '/^default / { print $NF }' |
+ sed 's/.* dev //')}
if is_network_root ; then
altdevs=$(find_alt_device $netdev)
for netdev in $altdevs; do break; done
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2007-11-07 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 11:58 [ANNOUNCE] Tree freeze for 3.2.0 Keir Fraser
2007-11-07 12:17 ` Yoni Yossef
2007-11-07 13:45 ` Keir Fraser
2007-11-07 12:49 ` Guillaume Rousse [this message]
2007-11-07 13:45 ` Keir Fraser
2007-11-07 16:33 ` Guillaume Rousse
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=4731B450.7000503@inria.fr \
--to=guillaume.rousse@inria.fr \
--cc=xen-devel@lists.xensource.com \
/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.