From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Marc-Andre Lureau" <mlureau@redhat.com>,
"Michael Tokarev" <mjt@tls.msk.ru>, QEMU <qemu-devel@nongnu.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Jeremy White" <jwhite@codeweavers.com>,
"David Airlie" <airlied@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] libcacard: move it to a standalone project
Date: Tue, 15 Sep 2015 14:46:24 +0100 [thread overview]
Message-ID: <20150915134624.GW23145@redhat.com> (raw)
In-Reply-To: <55F81F33.1050009@redhat.com>
On Tue, Sep 15, 2015 at 03:37:55PM +0200, Paolo Bonzini wrote:
> On 15/09/2015 15:28, Daniel P. Berrange wrote:
> > I have looked through the new libcacard git repository you created
> > from QEMU history, and reviewed the extra patches you added on top
> > for the build system and it all looks sane to me. So this this a
> >
> > Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
> >
> > for both the new GIT repo and also your proposed patch to switch
> > QEMU to use the new lib.
> >
> > I agree that it could make sense to host libcacard.git on git.qemu.org
> > if we're going to continue to use qemu-devel and a QEMU-like workflow,
> > but equally don't see any problem with it being a totally standalone
> > project with its own infra & practices.
>
> Where are we going to host virglrenderer? Whatever we do for libcacard,
> we should probably also do for virglrenderer.
I guess ultimately things like libcacard / virglrenderer are similar
to other projects we use like libiscsi, ibnfs, etcs. A reason for
splitting libcacard in particular is that it is used by more things
that just QEMU, so from that POV there's no clear compelling reason
for it to need to be hosted by QEMU. Probably the main reason for
keeping it hosted by QEMU would be to have some sense of shared
responsibility by the QEMU community in case Marc-Andre does not
want to be a single point person owning it long term.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2015-09-15 13:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 11:29 [Qemu-devel] [RFC PATCH] libcacard: move it to a standalone project marcandre.lureau
2015-09-10 17:47 ` Jeremy White
2015-09-15 11:50 ` Marc-André Lureau
2015-09-15 13:28 ` Daniel P. Berrange
2015-09-15 13:37 ` Paolo Bonzini
2015-09-15 13:46 ` Daniel P. Berrange [this message]
2015-09-15 21:53 ` Dave Airlie
2015-09-16 6:29 ` Gerd Hoffmann
2015-09-15 13:40 ` Peter Maydell
2015-09-22 11:06 ` Paolo Bonzini
2015-09-22 11:25 ` Marc-André Lureau
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=20150915134624.GW23145@redhat.com \
--to=berrange@redhat.com \
--cc=airlied@redhat.com \
--cc=armbru@redhat.com \
--cc=jwhite@codeweavers.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=mlureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).