qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, "Akihiko Odaki" <akihiko.odaki@daynix.com>,
	"Bibo Mao" <maobibo@loongson.cn>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: Giving your own patches your Reviewed-by
Date: Wed, 12 Mar 2025 10:45:33 +0000	[thread overview]
Message-ID: <Z9FlzR5xkTe1aOuW@redhat.com> (raw)
In-Reply-To: <878qpamvk6.fsf@pond.sub.org>

On Wed, Mar 12, 2025 at 10:45:29AM +0100, Markus Armbruster wrote:
> I stumbled over commits that carry the author's Reviewed-by.
> 
> There may be cases where the recorded author isn't the lone author, and
> the recorded author did some meaningful review of the patch's parts that
> are not theirs.  Mind that we do need all authors to provide their
> Signed-off-by.
> 
> When the only Signed-off-by is from the recorded author, and there's
> also their Reviewed-by, the Reviewed-by is almost certainly bogus.
> 
> Now, accidents happen, no big deal, etc., etc.  I post this to hopefully
> help reduce the accident rate :)

Is a commit with S-o-B and R-b from the matching author semantically any
different from a commit with an author S-o-B and NO other 3rd party tag
at all ?

The latter seems to be the more common case, with over a thousand examples
of commits with no 3rd party NNN-By tags.

$ cat > no-3rd-party.pl <<EOF
#!/usr/bin/perl

my @tags;
my $commit;
my $author;
while (<>) {
    if (/^commit ([a-z0-9]+)$/) {
	if (defined $commit) {
	    my $ok = 0;
	    foreach my $name (@tags) {
		if ($name ne $author) {
		    $ok = 1;
		    last;
		}
	    }
	    if (! $ok) {
		print ("$commit: $author\n");
	    }
	}
	
	$commit = $1;
	@tags = ();
    } elsif (/^Author:\s+(.*)$/) {
	$author = $1;
    } elsif (/\s+(Signed-off-by|Acked-by|Reviewed-by):\s+(.*)$/) {
	push @tags, $2;
    }
}
EOF
$ git log --no-merges --since 'two years ago'| perl no-rb.pl | wc -l
1296

That is 8% of all commits in 2 years seemingly having no 3rd party
review.

Pretty much all of our core maintainers have commits exhibiting this,
so I won't include any names.

Some of these will be just a case of forgetting to copy the R-bs
from the list.

I suspect most are just a case of a maintainer making a pragmmatic
judgement call to merge something having given up waiting for review,
and not wanting to badger people into reviewing.

Most appear to be fairly trivial patches which is good. So that 8% of
commits is probably at least an order of magnitude less lines of code
changed in that timeframe, and the less "risky" code at that.

With 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:[~2025-03-12 10:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12  9:45 Giving your own patches your Reviewed-by Markus Armbruster
2025-03-12 10:03 ` Philippe Mathieu-Daudé
2025-03-12 10:10   ` Markus Armbruster
2025-03-12 10:13   ` Daniel P. Berrangé
2025-03-12 12:54   ` Yi Liu
2025-03-13  6:45     ` CLEMENT MATHIEU--DRIF
2025-03-13  7:13       ` Markus Armbruster
2025-03-12 10:18 ` Philippe Mathieu-Daudé
2025-03-12 10:55   ` Markus Armbruster
2025-03-12 10:45 ` Daniel P. Berrangé [this message]
2025-03-12 10:56   ` Philippe Mathieu-Daudé
2025-03-13  1:21 ` bibo mao
2025-03-13  5:32   ` Markus Armbruster

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=Z9FlzR5xkTe1aOuW@redhat.com \
    --to=berrange@redhat.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=armbru@redhat.com \
    --cc=maobibo@loongson.cn \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).