From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Chetan Pant <chetan4windows@gmail.com>
Cc: qemu-trivial@nongnu.org, thuth@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/5] Fixing Lesser GPL version number [1/5]
Date: Fri, 9 Oct 2020 14:41:48 +0100 [thread overview]
Message-ID: <20201009134148.GB25901@redhat.com> (raw)
In-Reply-To: <20201009063734.2627-1-chetan4windows@gmail.com>
On Fri, Oct 09, 2020 at 06:37:34AM +0000, Chetan Pant wrote:
I'll take the following if you can split them up into a couple of
patches
> ---
> authz/base.c | 2 +-
> authz/list.c | 2 +-
> authz/listfile.c | 2 +-
> authz/pamacct.c | 2 +-
> authz/simple.c | 2 +-
Split these into an "authz" patch.
> block/crypto.c | 2 +-
> block/crypto.h | 2 +-
Split these two into a "crypto" patch.
> tests/io-channel-helpers.c | 2 +-
> tests/io-channel-helpers.h | 2 +-
Split these into an "io" patch.
Also combine with the io/* cleanups in patch 2, and the
tests/test-io-* cleanups later.
> tests/migration/guestperf-batch.py | 2 +-
> tests/migration/guestperf-plot.py | 2 +-
> tests/migration/guestperf.py | 2 +-
> tests/migration/guestperf/comparison.py | 2 +-
> tests/migration/guestperf/engine.py | 2 +-
> tests/migration/guestperf/hardware.py | 2 +-
> tests/migration/guestperf/plot.py | 2 +-
> tests/migration/guestperf/progress.py | 2 +-
> tests/migration/guestperf/report.py | 2 +-
> tests/migration/guestperf/scenario.py | 2 +-
> tests/migration/guestperf/shell.py | 2 +-
> tests/migration/guestperf/timings.py | 2 +-
> tests/migration/stress.c | 2 +-
Split these.
> tests/test-authz-list.c | 2 +-
> tests/test-authz-listfile.c | 2 +-
> tests/test-authz-pam.c | 2 +-
> tests/test-authz-simple.c | 2 +-
Include in "authz" patch.
> tests/test-crypto-afsplit.c | 2 +-
> tests/test-crypto-block.c | 2 +-
> tests/test-crypto-cipher.c | 2 +-
> tests/test-crypto-hash.c | 2 +-
> tests/test-crypto-ivgen.c | 2 +-
> tests/test-crypto-secret.c | 2 +-
> tests/test-crypto-xts.c | 2 +-
SPlit into a "crypto" patch
> tests/test-io-channel-buffer.c | 2 +-
> tests/test-io-channel-command.c | 2 +-
> tests/test-io-channel-file.c | 2 +-
> tests/test-io-channel-socket.c | 2 +-
> tests/test-io-task.c | 2 +-
Include in an "io" patch
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2020-10-09 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 6:37 [PATCH 1/5] Fixing Lesser GPL version number [1/5] Chetan Pant
2020-10-09 13:07 ` Eric Blake
2020-10-09 13:43 ` Daniel P. Berrangé
2020-10-09 14:25 ` Chetan
2020-10-09 13:41 ` Daniel P. Berrangé [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=20201009134148.GB25901@redhat.com \
--to=berrange@redhat.com \
--cc=chetan4windows@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.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 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).