From: Nivedita Singhvi <niv@us.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: xen-devel@lists.xensource.com, Robert Read <robert@xensource.com>,
Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Subject: Re: Re: [Xen-changelog] New console transport and update xenconsoled.
Date: Tue, 30 Aug 2005 12:20:04 -0700 [thread overview]
Message-ID: <4314B164.1050703@us.ibm.com> (raw)
In-Reply-To: <431490D4.20108@us.ibm.com>
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
prev parent reply other threads:[~2005-08-30 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EA8qJ-0002Zl-23@xenbits.xensource.com>
2005-08-30 17:01 ` [Xen-changelog] New console transport and update xenconsoled Anthony Liguori
2005-08-30 17:41 ` Christian Limpach
2005-08-30 20:17 ` Anthony Liguori
2005-08-31 8:52 ` Christian Limpach
2005-08-30 19:20 ` Nivedita Singhvi [this message]
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=4314B164.1050703@us.ibm.com \
--to=niv@us.ibm.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=aliguori@us.ibm.com \
--cc=robert@xensource.com \
--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.