qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Aleksandar Markovic <amarkovic@wavecomp.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"stefanha@redhat.com" <stefanha@redhat.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] Question: Perfecting checkpatch.pl
Date: Wed, 31 Oct 2018 12:00:49 +0000	[thread overview]
Message-ID: <20181031120049.GH9625@redhat.com> (raw)
In-Reply-To: <BN6PR2201MB1251EA1F1F5E486A889A827CC6CC0@BN6PR2201MB1251.namprd22.prod.outlook.com>

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.

 git log | grep -- '-by:' | sed -e 's/-by:.*/-by/' | sed -e 's/ //g' | sort | uniq -c
   3127 Acked-by
      1 ACKed-by
      1 Acked-off-by
      5 Analyzed-by
      3 Approximately-suggested-by
      3 Co-authored-by
      1 Edited-by
      2 eviewed-by
      1 Fine-with-me'd-by
      1 Fix-suggested-by
      3 Found-by
      1 Inspired-by
      1 Introduced-by
      1 Original-patch-by
      1 Problem-spotted-by
      2 Proposed-by
      2 Rebased-by
      1 Release-acked-by
      1 Reported-and-analyzed-by
      2 Reported-and-tested-by
      1 Reported-and-Tested-by
   1834 Reported-by
      1 Reportyed-by
      7 Requested-by
      2 Reveiwed-by
      1 Revieed-by
      2 Revieved-by
      4 Reviewd-by
  30991 Reviewed-by
      2 Reviewed-off-by
      3 Reviwed-by
      1 Rported-by
      1 Sgined-off-by
      1 Sigend-off-by
      1 Signed-by
      1 Signed-of-by
  97837 Signed-off-by
      1 Signer-off-by
      4 Singed-off-by
      1 Spotted-by
    660 Suggested-by
   1951 Tested-by
      1 Tested-off-by
      1 xSigned-off-by


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 :|

  parent reply	other threads:[~2018-10-31 12:01 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é [this message]
2018-10-31 13:27   ` Peter Maydell
2018-10-31 13:33     ` Daniel P. Berrangé

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=20181031120049.GH9625@redhat.com \
    --to=berrange@redhat.com \
    --cc=amarkovic@wavecomp.com \
    --cc=pbonzini@redhat.com \
    --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).