From: Kashyap Chamarthy <kchamart@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Daniel Berrange <berrange@redhat.com>,
Beraldo Leal <bleal@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
Cleber Rosa <crosa@redhat.com>, Eric Blake <eblake@redhat.com>
Subject: Re: [qemu.qmp PATCH 02/13] fork qemu.qmp from qemu.git
Date: Tue, 5 Apr 2022 10:50:56 +0200 [thread overview]
Message-ID: <YkwC8Hg6bs+PVpQk@paraplu> (raw)
In-Reply-To: <CAFn=p-ZQvyyStRPo_6mgTKm7X1w9fu0KqfhmUHK7cYTCC_mmyw@mail.gmail.com>
On Mon, Apr 04, 2022 at 02:56:10PM -0400, John Snow wrote:
> On Mon, Apr 4, 2022 at 2:54 PM John Snow <jsnow@redhat.com> wrote:
[...]
> > > > .gitignore | 2 +-
> > > > Makefile | 16 ++++++++--------
> > > > setup.cfg | 24 +-----------------------
> > > > setup.py | 2 +-
> > > > 4 files changed, 11 insertions(+), 33 deletions(-)
> > >
> > > The changes here look fine to me (and thanks for making it a "micro
> > > change"). I'll let sharper eyes than mine to give a closer look at the
> > > `git filter-repo` surgery. Although, that looks fine to me too.
> > >
> > > [...]
> > >
> > > > .PHONY: distclean
> > > > distclean: clean
> > > > - rm -rf qemu.egg-info/ .venv/ .tox/ $(QEMU_VENV_DIR) dist/
> > > > + rm -rf qemu.qmp.egg-info/ .venv/ .tox/ $(QEMU_VENV_DIR) dist/
> > > > rm -f .coverage .coverage.*
> > > > rm -rf htmlcov/
> > > > diff --git a/setup.cfg b/setup.cfg
> > > > index e877ea5..4ffab73 100644
> > > > --- a/setup.cfg
> > > > +++ b/setup.cfg
> > > > @@ -1,5 +1,5 @@
> > > > [metadata]
> > > > -name = qemu
> > > > +name = qemu.qmp
> > > > version = file:VERSION
> > > > maintainer = QEMU Developer Team
> > >
> > > In the spirit of patch 04 ("update maintainer metadata"), do you also
> > > want to update here too? s/QEMU Developer Team/QEMU Project?
> > >
> >
> > Good spot.
>
> ...Or, uh. That's exactly what I update in patch 04. Are you asking me
> to fold in that change earlier? I'm confused now.
Oops, perils of reviewing late in the day. I missed to notice it's the
same file. You're right; please ignore my remark. Sorry for the noise.
--
/kashyap
next prev parent reply other threads:[~2022-04-05 8:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 18:24 [qemu.qmp PATCH 00/13] python: fork qemu.qmp python lib into independent repo John Snow
2022-03-30 18:24 ` [qemu.qmp PATCH 01/13] pylint hotfix John Snow
2022-03-30 18:24 ` [qemu.qmp PATCH 02/13] fork qemu.qmp from qemu.git John Snow
2022-04-01 17:05 ` Kashyap Chamarthy
2022-04-04 18:54 ` John Snow
2022-04-04 18:56 ` John Snow
2022-04-05 8:50 ` Kashyap Chamarthy [this message]
2022-04-05 15:28 ` John Snow
2022-03-30 18:24 ` [qemu.qmp PATCH 03/13] update VERSION to 0.0.0a1 John Snow
2022-03-30 18:24 ` [qemu.qmp PATCH 04/13] update maintainer metadata John Snow
2022-03-30 18:24 ` [qemu.qmp PATCH 05/13] update project description John Snow
2022-04-01 16:52 ` Beraldo Leal
2022-03-30 18:24 ` [qemu.qmp PATCH 06/13] [FIXME] update project URLs John Snow
2022-03-30 18:24 ` [qemu.qmp PATCH 07/13] add a couple new trove classifiers John Snow
2022-04-01 16:54 ` Beraldo Leal
2022-03-30 18:24 ` [qemu.qmp PATCH 08/13] move README.rst to FILES.rst and update John Snow
2022-03-30 18:24 ` [qemu.qmp PATCH 09/13] [FIXME] move PACKAGE.rst to README.rst " John Snow
2022-04-01 16:40 ` Kashyap Chamarthy
2022-04-01 17:31 ` John Snow
2022-03-30 18:24 ` [qemu.qmp PATCH 10/13] docs: add versioning policy to README John Snow
2022-04-05 9:16 ` Damien Hedde
2022-04-05 15:47 ` John Snow
2022-03-30 18:24 ` [qemu.qmp PATCH 11/13] add LGPLv2+ and GPLv2 LICENSE files John Snow
2022-03-30 18:24 ` [qemu.qmp PATCH 12/13] update Pipfile John Snow
2022-03-30 18:24 ` [qemu.qmp PATCH 13/13] remove sub-dependency pins from Pipfile John Snow
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=YkwC8Hg6bs+PVpQk@paraplu \
--to=kchamart@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@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).