From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Aleksandar Markovic <amarkovic@wavecomp.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"stefanha@redhat.com" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Question: Perfecting checkpatch.pl
Date: Wed, 31 Oct 2018 13:33:34 +0000 [thread overview]
Message-ID: <20181031133334.GL9625@redhat.com> (raw)
In-Reply-To: <CAFEAcA-20HUdGyNYFoqzhPdBbxpJ5iRH+F0WWNwgjs=JpsN7Xw@mail.gmail.com>
On Wed, Oct 31, 2018 at 01:27:15PM +0000, Peter Maydell wrote:
> On 31 October 2018 at 12:00, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > On Tue, Oct 30, 2018 at 12:35:15PM +0000, Aleksandar Markovic wrote:
> >> Perhaps checkpatch.pl should make sure the commit messages do not contain "address@hidden" and "Reviewed-off-by"?
> >>
> >> $ git log | grep address@hidden
> >> Signed-off-by: Michael S. Tsirkin <address@hidden>
> >> Signed-off-by: Ronald Hecht <address@hidden>
> >> Signed-off-by: Justin Chevrier <address@hidden>
> >> Signed-off-by: Justin Chevrier <address@hidden>
> >> Signed-off-by: Justin Chevrier <address@hidden>
> >
> > This makes sense...
> >
> >>
> >> $ git log | grep Reviewed-off-by
> >> Reviewed-off-by: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>
> >> Reviewed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> >
> > but I'm not convinced it is worth doing this, because the set of
> > mistakes people have made is enourmous, so it turns into a game
> > of whack-a-mole.
>
> You could have checkpatch whitelist the sensible ones:
>
> > 3127 Acked-by
> > 1834 Reported-by
> > 30991 Reviewed-by
> > 97837 Signed-off-by
> > 660 Suggested-by
> > 1951 Tested-by
>
> and warn about the rest...
I guess warning would be ok - I don't want to discourage people from
being creative and "singing off" their patches :-)
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:[~2018-10-31 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 12:35 [Qemu-devel] Question: Perfecting checkpatch.pl Aleksandar Markovic
2018-10-30 13:17 ` Paolo Bonzini
2018-10-30 14:48 ` Aleksandar Markovic
2018-10-30 15:02 ` Peter Maydell
2018-10-30 13:21 ` Philippe Mathieu-Daudé
2018-10-31 12:00 ` Daniel P. Berrangé
2018-10-31 13:27 ` Peter Maydell
2018-10-31 13:33 ` 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=20181031133334.GL9625@redhat.com \
--to=berrange@redhat.com \
--cc=amarkovic@wavecomp.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).