From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Michael Tokarev <mjt@tls.msk.ru>, QEMU <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
Jeremy White <jwhite@codeweavers.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] libcacard: move it to a standalone project
Date: Tue, 15 Sep 2015 14:28:26 +0100 [thread overview]
Message-ID: <20150915132826.GV23145@redhat.com> (raw)
In-Reply-To: <CAJ+F1CLEDPEuUXwmPrSjKyD8HLDNM_gwU+K+Qz62eWiPX4EEJQ@mail.gmail.com>
On Tue, Sep 15, 2015 at 01:50:15PM +0200, Marc-André Lureau wrote:
> Hi
>
> (added in CC people from the "libcacard: use the library?" thread)
>
> On Thu, Sep 10, 2015 at 7:47 PM, Jeremy White <jwhite@codeweavers.com> wrote:
> > On 08/30/2015 06:29 AM, marcandre.lureau@redhat.com wrote:
> >> From: Marc-André Lureau <marcandre.lureau@redhat.com>
> >>
> >> As previously discussed in the thread "libcacard: use the library?",
> >> make libcacard a standalone library and use it if --enable-smartcard.
> >>
> >> I made the following repo out of a qemu filter-branch and added autofoo
> >> build-sys: https://github.com/elmarco/libcacard. Since the original qemu
> >> git tags are there, I think the first release version should be v2.5,
> >> but there is no need to follow the same versions as qemu later on.
> >>
> >> libcacard could use the same infrastructure as the qemu project (mailing
> >> list, git server, reviews etc). I have some experience with libcacard,
> >> and I would be willing to maintain it, however I don't expect to do
> >> more development with it in the near future.
> >>
> >> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> >
> > I have reviewed this patch, and the new libcacard module. Modulo a few
> > minor nits (which Marc-André agreed to fix on irc), it all works well.
> > I think this is a sensible change and I'm willing to help with
> > libcacard maintenance, if we were to establish it as a project.
> >
> > Reviewed-by: Jeremy White <jwhite@codeweavers.com>
>
> In order to progress with this removal, I propose we move
> https://github.com/elmarco/libcacard master to git.qemu.org. Then make
> a 2.4.1 release (ie same as 2.4 but standalone), make a wiki page
> about libcacard etc. Then I can send a non-RFC patch to qemu, and we
> can keep maintaining libcacard within qemu project. I have pending
> patches in the next tree that I can send on the ML for review etc.
>
> What do you think?
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.
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:28 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 [this message]
2015-09-15 13:37 ` Paolo Bonzini
2015-09-15 13:46 ` Daniel P. Berrange
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=20150915132826.GV23145@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=jwhite@codeweavers.com \
--cc=marcandre.lureau@gmail.com \
--cc=mjt@tls.msk.ru \
--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).