unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>,
	 Florian Weimer <fweimer@redhat.com>
Subject: Re: How to keep Reviewed-by lines in git commits with gerrit.
Date: Tue, 12 Nov 2019 20:07:27 +0100	[thread overview]
Message-ID: <87lfskgbgw.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <7b4aa5d2-14e7-c0aa-a258-bbd60455fae5@redhat.com> (Carlos O'Donell's message of "Tue, 12 Nov 2019 12:35:36 -0500")

* Carlos O'Donell:

> If we ever switch to supporting Gerrit, then we will automatically
> gain the Reviewed-by: lines depending on the configuration of Gerrit.
> Reviewers would understand this as part of doing their reviews and
> granting the review +1/+2.
>
> In the meantime I can do two things as a reviewer to help you keep
> the Reviewed-by lines.
>
> 1. If I am about to grant +2 review I edit the commit and generate
>    a new patchset version, and add my Reviewed-by line.
> 2. I submit my review of +2.
>
> Then when you push, you just need to make sure your new commit message
> matches and it should close the review.

We should not edit the commit message manually after it has been
reviewed.

Either it is automatically added by the review tool, or we need to
gather patch review statistics from the review tool.

The latter has the advantage that post-commit review also counts,
which is not possible if we only consider Reviewed-By: lines in
commits.

  parent reply	other threads:[~2019-11-12 19:07 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 17:35 How to keep Reviewed-by lines in git commits with gerrit Carlos O'Donell
2019-11-12 17:40 ` Joseph Myers
2019-11-12 19:05   ` Carlos O'Donell
2019-11-12 22:26     ` Joseph Myers
2019-11-12 22:35       ` Florian Weimer
2019-11-12 22:47         ` Joseph Myers
2019-11-12 19:07 ` Florian Weimer [this message]
2019-11-12 19:30   ` Carlos O'Donell
2019-11-12 19:39     ` Florian Weimer
2019-11-12 19:59       ` Jonathan Nieder
2019-11-12 20:02         ` Florian Weimer
2019-11-12 20:08           ` Jonathan Nieder
2019-11-12 20:14             ` Florian Weimer
2019-11-12 20:42               ` Carlos O'Donell
2019-11-12 20:56                 ` Florian Weimer
2019-11-12 20:48         ` Florian Weimer
2019-11-12 21:04           ` Carlos O'Donell
2019-11-12 21:10           ` Florian Weimer
2019-11-12 22:11             ` Carlos O'Donell
2019-11-13 13:39               ` Siddhesh Poyarekar
2019-11-13 17:20               ` Tulio Magno Quites Machado Filho
2019-11-13 17:33                 ` Florian Weimer
2019-11-13  3:29         ` Carlos O'Donell
2019-11-13 18:16           ` Joseph Myers
2019-11-13 18:18             ` Florian Weimer
2019-11-13 21:38           ` Jonathan Nieder
2019-11-13 23:31             ` Jonathan Nieder
2019-11-12 20:40       ` Carlos O'Donell
2019-11-12 20:57         ` Florian Weimer
2019-11-12 21:09           ` Carlos O'Donell
2019-11-12 21:19             ` Florian Weimer
2019-11-12 21:20               ` Carlos O'Donell
2019-11-12 21:21                 ` Florian Weimer
2019-11-12 21:22                   ` Carlos O'Donell
2019-11-12 21:23                     ` Florian Weimer

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lfskgbgw.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).