From: Avi Kivity <avi@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu list <qemu-devel@nongnu.org>, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/7] iohandlers: Mark current implementation as 'old'
Date: Tue, 22 Feb 2011 16:43:59 +0200 [thread overview]
Message-ID: <4D63CBAF.8030203@redhat.com> (raw)
In-Reply-To: <20110222143726.GA4939@amit-x200.redhat.com>
On 02/22/2011 04:37 PM, Amit Shah wrote:
> On (Tue) 22 Feb 2011 [15:28:59], Avi Kivity wrote:
> > On 02/22/2011 01:17 PM, Amit Shah wrote:
> > >On (Tue) 22 Feb 2011 [13:09:34], Avi Kivity wrote:
> > >> On 02/22/2011 12:18 PM, Amit Shah wrote:
> > >> >Mark the current iohandler list as 'old'. In the next commit we'll
> > >> >introduce a new iohandler api that will replace the list name.
> > >> >
> > >> >The 'old' list will eventually be completely replaced by the new
> > >> >implementation.
> > >>
> > >> A better way to do this is to implement the old API in terms of the
> > >> new API. This ensures you don't lose any functionality, and reduces
> > >> the amount of low-level infrastructure.
> > >
> > >With this new approach of switching to just one callback, that is more
> > >work for little gain as we'll just deprecate the older API soon. (The
> > >previous patches used this approach, btw.)
> >
> > Does "deprecate" mean "completely remove"?
> >
> > If so I agree.
>
> Yes, completely removing the older API is the plan (as noted in
> message 00).
Great. That's a much better deprecate than "add the new thing and let
the old thing rot" (which I've been guilty of a few times).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-22 14:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 10:18 [Qemu-devel] [PATCH 0/7] New iohandler API Amit Shah
2011-02-22 10:18 ` [Qemu-devel] [PATCH 1/7] iohandlers: Mark current implementation as 'old' Amit Shah
2011-02-22 11:09 ` Avi Kivity
2011-02-22 11:17 ` Amit Shah
2011-02-22 13:28 ` Avi Kivity
2011-02-22 14:37 ` Amit Shah
2011-02-22 14:43 ` Avi Kivity [this message]
2011-02-22 10:18 ` [Qemu-devel] [PATCH 2/7] iohandlers: Introduce a new API Amit Shah
2011-02-22 12:39 ` Alon Levy
2011-02-22 13:09 ` Amit Shah
2011-02-22 13:28 ` Avi Kivity
2011-02-22 14:39 ` Amit Shah
2011-02-22 15:00 ` Anthony Liguori
2011-02-22 16:21 ` Avi Kivity
2011-02-22 18:21 ` Anthony Liguori
2011-02-23 12:40 ` Avi Kivity
2011-02-22 14:49 ` [Qemu-devel] " Anthony Liguori
2011-02-22 10:18 ` [Qemu-devel] [PATCH 3/7] char: tcp: Use new iohandler api Amit Shah
2011-02-22 10:18 ` [Qemu-devel] [PATCH 4/7] char: udp: " Amit Shah
2011-02-22 10:18 ` [Qemu-devel] [PATCH 5/7] char: fd: " Amit Shah
2011-02-22 10:18 ` [Qemu-devel] [PATCH 6/7] char: stdio: " Amit Shah
2011-02-22 10:18 ` [Qemu-devel] [PATCH 7/7] char: pty: " Amit Shah
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=4D63CBAF.8030203@redhat.com \
--to=avi@redhat.com \
--cc=amit.shah@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).