[ANNOUNCE] Tree freeze for 3.2.0

[ANNOUNCE] Tree freeze for 3.2.0

[Keir Fraser]

Folks,

I've now finished committing new features into xen-unstable and the tree is
now frozen until after 3.2.0 is released in the next few weeks. No new
features will be accepted at this time; this also applies to the following
pending patches: MSI support (Intel), machine-check support (AMD), PV
scsifront/scsiback (Fujitsu).

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!

 -- Keir

RE: [ANNOUNCE] Tree freeze for 3.2.0

[Yoni Yossef]

Hi Keir,

My name is Yony, I'm developing Mellanox support for Xen - InfiniBand
and Ethernet.

How do I download the source tree in order to test it?

Yehonatan Yossef
Mellanox Technologies LTD
Tel: +972-4-9097200 ext. 301
Cell: 054-2345031

-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser
Sent: Wednesday, November 07, 2007 1:59 PM
To: xen-devel
Subject: [Xen-devel] [ANNOUNCE] Tree freeze for 3.2.0

Folks,

I've now finished committing new features into xen-unstable and the tree
is now frozen until after 3.2.0 is released in the next few weeks. No
new features will be accepted at this time; this also applies to the
following pending patches: MSI support (Intel), machine-check support
(AMD), PV scsifront/scsiback (Fujitsu).

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!

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: [ANNOUNCE] Tree freeze for 3.2.0

[Keir Fraser]

Make sure you have mercurial installed, and then 'hg clone
http://xenbits.xensource.com/xen-unstable.hg'.

 -- Keir

On 7/11/07 12:17, "Yoni Yossef" <yoniy@mellanox.co.il> wrote:

> Hi Keir,
> 
> My name is Yony, I'm developing Mellanox support for Xen - InfiniBand
> and Ethernet.
> 
> How do I download the source tree in order to test it?
> 
> Yehonatan Yossef
> Mellanox Technologies LTD
> Tel: +972-4-9097200 ext. 301
> Cell: 054-2345031
> 
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Keir Fraser
> Sent: Wednesday, November 07, 2007 1:59 PM
> To: xen-devel
> Subject: [Xen-devel] [ANNOUNCE] Tree freeze for 3.2.0
> 
> Folks,
> 
> I've now finished committing new features into xen-unstable and the tree
> is now frozen until after 3.2.0 is released in the next few weeks. No
> new features will be accepted at this time; this also applies to the
> following pending patches: MSI support (Intel), machine-check support
> (AMD), PV scsifront/scsiback (Fujitsu).
> 
> 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!
> 
>  -- Keir
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: [ANNOUNCE] Tree freeze for 3.2.0

[Guillaume Rousse]

[-- 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

Re: [ANNOUNCE] Tree freeze for 3.2.0

[Keir Fraser]

On 7/11/07 12:49, "Guillaume Rousse" <Guillaume.Rousse@inria.fr> wrote:

> 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.

The code in the tree looks like your patch has been applied, yes. You can
always check for yourself, of course.

 -- Keir

Re: [ANNOUNCE] Tree freeze for 3.2.0

[Guillaume Rousse]

[-- Attachment #1: Type: text/plain, Size: 638 bytes --]

Keir Fraser a écrit :
> On 7/11/07 12:49, "Guillaume Rousse" <Guillaume.Rousse@inria.fr> wrote:
> 
>> 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.
> 
> The code in the tree looks like your patch has been applied, yes. You can
> always check for yourself, of course.
The patch was reversed, sorry (/me sux).

here is the correct one.
-- 
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:37:55.000000000 +0100
+++ network-bridge	2007-11-07 13:46:30.000000000 +0100
@@ -72,8 +72,8 @@
     echo "$ifs"
 }
 
-netdev=${netdev:-$(ip route list | awk '/^default / { print $NF }' |
-		   sed 's/.* dev //')}
+netdev=${netdev:-$(ip route list 0.0.0.0/0  | \
+                   sed 's/.*dev \([a-z]\+[0-9]\+\).*$/\1/')}
 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