From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nivedita Singhvi Subject: Re: Re: [Xen-changelog] New console transport and update xenconsoled. Date: Tue, 30 Aug 2005 12:20:04 -0700 Message-ID: <4314B164.1050703@us.ibm.com> References: <431490D4.20108@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <431490D4.20108@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Anthony Liguori Cc: xen-devel@lists.xensource.com, Robert Read , Christian Limpach List-Id: xen-devel@lists.xenproject.org Anthony Liguori wrote: > Also, there's a number of errors that this code introduces (changing > things to use asprintf and not checking for OOM conditions). It would > have been nice if this went to the list first so we could comment on it. I'd also like to add another request. I know the Xen mode of operation is "if you're using xen-unstable, follow the commits-list for changes." However, this is turning out to be somewhat painful. I don't want to add further burden on developers who are putting out this code, but it would really, really help us to get a line or two on xen-devel as a head's up that some code has gone in and changed the way some user-visible piece works. Sometimes, this isn't obvious from the list and sometimes, it's not possible for all the users (quite a few who are on xen-unstable) to track check-ins. Documentation would be good, too :). thanks, Nivedita