From: Rob Landley <rob@landley.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] RFC: This project needs a stable branch
Date: Thu, 22 Mar 2007 19:23:09 -0400 [thread overview]
Message-ID: <200703221923.09691.rob@landley.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0703230000170.4045@wbgn013.biozentrum.uni-wuerzburg.de>
On Thursday 22 March 2007 7:00 pm, Johannes Schindelin wrote:
> Hi,
>
> On Thu, 22 Mar 2007, Rob Landley wrote:
>
> > On Tuesday 20 March 2007 6:19 pm, Julian Seward wrote:
> > > Limited effort is always a problem, granted.
> > >
> > > So here's a broader question, which I'm surprised nobody has asked
> > > before (afaik). Think forward to a hypothetical QEMU 1.0 release.
> > > What criteria are required for such a release?
> >
> > *cough* *cough* QOPS *cough* *cough*
>
> *cough* *cough* patches? *cough* *cough*
Do you mean you're asking me to break up Paul Brook's QOPS tree at
https://nowt.dyndns.org and submit it to mainline? I can do this thing, if
you really think it would help. Seems a bit roundabout to submit Paul
Brook's work to Paul Brook, though, when he has CVS commit access and I
don't.
Rob
--
Vista: Windows Millenium Second Edition
next prev parent reply other threads:[~2007-03-22 23:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 11:11 [Qemu-devel] RFC: This project needs a stable branch Julian Seward
2007-03-15 13:48 ` Anthony Liguori
2007-03-15 14:11 ` Julian Seward
2007-03-15 14:53 ` Paul Brook
2007-03-15 15:34 ` Avi Kivity
2007-03-20 22:19 ` Julian Seward
2007-03-22 22:47 ` Rob Landley
2007-03-22 23:00 ` Johannes Schindelin
2007-03-22 23:23 ` Rob Landley [this message]
2007-03-22 23:27 ` Paul Brook
2007-03-22 23:57 ` Julian Seward
2007-03-23 0:35 ` Paul Brook
2007-03-23 0:37 ` Johannes Schindelin
2007-03-22 23:29 ` Thiemo Seufer
2007-03-22 23:45 ` Rob Landley
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=200703221923.09691.rob@landley.net \
--to=rob@landley.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=paul@codesourcery.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).