From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nivedita Singhvi <niv@us.ibm.com>
Subject: Re: Change in xm interface
Date: Fri, 17 Feb 2006 14:25:57 -0800
Message-ID: <43F64D75.8030200@us.ibm.com>
References: <43F63AB8.6070407@us.ibm.com>
	<20060217215805.GI3848@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20060217215805.GI3848@localhost.localdomain>
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: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Ewan Mellor wrote:

>>Perhaps this sort of changes should be announced on xen-announce in the 
>>future?  Is there such a list?
> 
> 
> That list is xen-devel, for the moment.  I'm not sure there's any value
> in having a separate list -- anyone who's developing products that sit
> on top of Xen _really_ needs to be reading xen-devel anyway -- the
> project simply isn't mature enough for you to get away without doing
> that.

Heavily seconded. Please don't fork mailing lists - it really
isn't warranted, and tends to exaggerate the problem we're
trying to solve (people not seeing the information they need
because it's hidden somewhere)...

thanks,
Nivedita