From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] scripts: let checkpatch.pl process an entire GIT branch
Date: Tue, 12 Sep 2017 18:24:22 +0200 [thread overview]
Message-ID: <76f6207d-165d-d1dd-652f-67038e9f2509@redhat.com> (raw)
In-Reply-To: <20170912162223.GN17633@redhat.com>
On 12/09/2017 18:22, Daniel P. Berrange wrote:
> On Tue, Sep 12, 2017 at 06:14:57PM +0200, Paolo Bonzini wrote:
>> On 12/09/2017 18:12, Daniel P. Berrange wrote:
>>> On Tue, Sep 12, 2017 at 05:52:18PM +0200, Paolo Bonzini wrote:
>>>> On 12/09/2017 12:46, 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 new
>>>>> flag '--branch' to checkpatch.pl which instructs it to check every
>>>>> patch on the current GIT branch.
>>>>
>>>> Great idea, though I'm not sure about having a default. And to keep it
>>>> easy to invoke, having a sole argument that ends with ".." might DWIM
>>>> and enable --branch too...
>>>
>>> I think it is beneficial to have a default, as I figure the majority
>>> of contributors are working on a branch that's rebased against master..
>>> Half as many characters to type in the common case :-)
>>
>> With the DWIM option "--branch" and "master.." are exactly the same
>> length. :)
>
> Oh hang on. I think I misunderstood what you suggested. I thought you
> meant 'checkpatch.pl --branch master..', but IIUC you actually mean
> 'checkpatch.pl master..' with no flag. That would work with me.
Yes, basically if length(argv) == 1 and argv[0] ends with ".." then
enable branch. The default for --branch with no ARGV could be
"origin/master.."---or it could ask git-config for the upstream tracking
branch but maybe that's too much to ask.
Paolo
next prev parent reply other threads:[~2017-09-12 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 10:46 [Qemu-devel] [PATCH] scripts: let checkpatch.pl process an entire GIT branch Daniel P. Berrange
2017-09-12 15:52 ` Paolo Bonzini
2017-09-12 16:12 ` Daniel P. Berrange
2017-09-12 16:14 ` Paolo Bonzini
2017-09-12 16:22 ` Daniel P. Berrange
2017-09-12 16:24 ` Paolo Bonzini [this message]
2017-09-12 18:05 ` 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=76f6207d-165d-d1dd-652f-67038e9f2509@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@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).