From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] scripts: let checkpatch.pl process an entire GIT branch
Date: Wed, 13 Sep 2017 09:05:47 +0100 [thread overview]
Message-ID: <20170913080547.GA3067@redhat.com> (raw)
In-Reply-To: <1a39aeeb-1362-4fdb-4bee-b11a258954f5@redhat.com>
On Tue, Sep 12, 2017 at 07:11:34PM +0200, Paolo Bonzini wrote:
> On 12/09/2017 18:51, Daniel P. Berrange wrote:
> > Currently before submitting a series, devs should run checkpatch.pl
> > across each patch to be submitted. This can be automated using a
> > command such as:
> >
> > git rebase -i master -x 'git show | ./scripts/checkpatch.pl -'
> >
> > This is rather long winded to type, so this patch introduces a way
> > to tell checkpatch.pl to validate a series of GIT revisions.
> >
> > If checkpatch.pl is given a single argument that contains a literal
> > '..', this is interpreted as a GIT revision list.
> >
> > For example:
> >
> > $ ./scripts/checkpatch.pl master..
> > total: 0 errors, 0 warnings, 297 lines checked
> >
> > b886d352a2bf58f0996471fb3991a138373a2957 has no obvious style problems and is ready for submission.
> > total: 0 errors, 0 warnings, 182 lines checked
> >
> > 2a731f9a9ce145e0e0df6d42dd2a3ce4dfc543fa has no obvious style problems and is ready for submission.
> > total: 0 errors, 0 warnings, 102 lines checked
> >
> > 11844169bcc0c8ed4449eb3744a69877ed329dd7 has no obvious style problems and is ready for submission.
> >
> > If a genuine patch filename contains the characters '..' it is
> > possible to force interpretation of the arg as a patch
> >
> > $ ./scripts/checkpatch.pl --patch master..
> >
> > will force it to load a patch file called "master.."
>
> Looks good, but why no --branch anymore? :) (I can also try adding it
> back on top).
It felt redundant to me. I guess it could be used to force interpretation
of the arg as a git revlist, even if it lacks '..' ?
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:[~2017-09-13 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 16:51 [Qemu-devel] [PATCH v2] scripts: let checkpatch.pl process an entire GIT branch Daniel P. Berrange
2017-09-12 17:11 ` Paolo Bonzini
2017-09-13 8:05 ` Daniel P. Berrange [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=20170913080547.GA3067@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.