git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>, git <git@vger.kernel.org>
Subject: Re: Upstreaming Reviewed-by to git.git
Date: Mon, 29 Mar 2021 14:03:53 -0700	[thread overview]
Message-ID: <xmqqr1jxisee.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD1TmckvQLVQ7eWMKakMKOF76J+Z+E25vUCGkWveXMWv1g@mail.gmail.com> (Christian Couder's message of "Mon, 29 Mar 2021 14:15:17 +0200")

Christian Couder <christian.couder@gmail.com> writes:

> On Mon, Mar 29, 2021 at 1:03 PM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
>> I had reviewing patches here, but how can my reviews be credited with
>> Reviewed-by tags to the applicable patches on git.git (Git SCM)
>> repo (upstream)?
>
> When you have reviewed a patch or a patch series, you can tell the
> reviewer you are ok with the patch or patch series, and that you are
> ok with them adding your "Reviewed-by: yourname <youremail>" to it.

I think you meant "you can tell the reviewEE", not reviewer.

In general, anybody can review a patch, but a review by somebody who
is not all that familiar with the codebase does not carry a lot of
weight.  Reviews from those who have already invested a lot in the
code that is being fixed or extended would obviously be very
helpful, as they are expected to know how the current code is
supposed to work well, and reviews from those who have worked on
other parts of the system that depend on the code that is being
fixed or extended would also be usefl, as they know what the callers
of the code being changed expect out of it.

So my suggestion to Bagas is not to worry too much about
"Reviewed-by" with your name, until you have your own code in the
codebase (and while doing so, you should worry about adding
reviewed-by by others).

In any case, reading others' patch, together with the original
version before the patch changed, is a great opportunity to learn
the codebase and how the project work in general.  It is highly
recommended.

Thanks.

  reply	other threads:[~2021-03-29 21:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 10:56 Upstreaming Reviewed-by to git.git Bagas Sanjaya
2021-03-29 12:15 ` Christian Couder
2021-03-29 21:03   ` Junio C Hamano [this message]
2021-03-30  0:43     ` Junio C Hamano
2021-03-30  7:21     ` Christian Couder

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: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqr1jxisee.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=bagasdotme@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).