From mboxrd@z Thu Jan  1 00:00:00 1970
From: Patrick Scharrenberg <pittipatti@web.de>
Subject: Re: RE: New Release Process
Date: Wed, 25 Jan 2006 10:59:18 +0100
Message-ID: <43D74BF6.9010709@web.de>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D40A331@liverpoolst.ad.cl.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D40A331@liverpoolst.ad.cl.cam.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Hi Ian!


> > There are a couple of bugs I'd really like to see fixed ASAP: 
> > [...]
> >  * investigate the reported memory leak with some routed network configs
> > [...]
>   
This seems to be fixed. I run this server for ~6 days now with the
unstable code from ~6days ago and the same config.
Since I couln't see the memory leak anymore I thought you fixed it earlier.

Patrick