From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, andrew@lunn.ch,
jesse.brandeburg@intel.com, sd@queasysnail.net,
horms@verge.net.au, przemyslaw.kitszel@intel.com,
f.fainelli@gmail.com, jiri@resnulli.us, ecree.xilinx@gmail.com
Subject: Re: [PATCH net-next v2] docs: try to encourage (netdev?) reviewers
Date: Wed, 11 Oct 2023 15:47:33 +0700 [thread overview]
Message-ID: <ZSZhJW92xsLVdtFw@debian.me> (raw)
In-Reply-To: <20231011024224.161282-1-kuba@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]
On Tue, Oct 10, 2023 at 07:42:24PM -0700, Jakub Kicinski wrote:
> +Another technique that is useful in case of a disagreement is to ask for others
> +to chime in. If a discussion reaches a stalemate after a few exchanges,
> +then call for opinions of other reviewers or maintainers. Often those in
> +agreement with a reviewer remain silent unless called upon.
> +The opinion of multiple people carries exponentially more weight.
or no conclusing replies?
> +
> +There is no strict requirement to use specific tags like ``Reviewed-by``.
> +In fact reviews in plain English are more informative and encouraged
> +even when a tag is provided, e.g. "I looked at aspects A, B and C of this
> +submission and it looks good to me."
> +Some form of a review message or reply is obviously necessary otherwise
> +maintainers will not know that the reviewer has looked at the patch at all!
> +
So a bare Reviewed-by: tag is enough to be a reviewer, right?
> +Last but not least patch review may become a negative process, focused
> +on pointing out problems. Please throw in a compliment once in a while,
> +particularly for newbies!
... to encourage them contributing more.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-11 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 2:42 [PATCH net-next v2] docs: try to encourage (netdev?) reviewers Jakub Kicinski
2023-10-11 8:47 ` Bagas Sanjaya [this message]
2023-10-12 0:14 ` Florian Fainelli
2023-10-12 7:55 ` Martin Habets
2023-10-15 13:30 ` patchwork-bot+netdevbpf
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=ZSZhJW92xsLVdtFw@debian.me \
--to=bagasdotme@gmail.com \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=horms@verge.net.au \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sd@queasysnail.net \
--cc=workflows@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.
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).