git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] ReviewingGuidelines: encourage positive reviews more

From
Patrick Steinhardt <ps@pks.im>
Date
Jul 25, 2024, 06:51 UTC
Message-ID
<ZqH2DK83PoU2786-@tanuki>
In-Reply-To
<xmqqsevysdaa.fsf@gitster.g>
On Wed, Jul 24, 2024 at 02:14:37PM -0700, Junio C Hamano wrote:
Show 5 quoted lines
> I saw some contributors hesitate to give a positive review on
> patches by their coworkers.  When written well, a positive review
> does not have to be a hollow "looks good" that rubber stamps an
> otherwise useless approval on a topic that is not interesting to
> anybody.

Oh, yes, this addition is very welcome indeed! It's a painpoint of ours at GitLab, and folks were indeed quite unsure about how to handle positive reviews. I was trying to guide them into the direction of "reverbalizing" and "thinking out aloud" parts of a patch series that are tricky in order to demonstrate that they have indeed read through the patches and understand them. Having all of this written down explicitly should hopefully help them.

Except for the typo mentioned by Eric I don't have anything else to add. Thanks!

Patrick
Previous: Eric SunshineNext: Derrick Stolee
Message 3 of 8 in “ReviewingGuidelines: encourage positive reviews more”
  1. ReviewingGuidelines: encourage positive reviews moreJunio C Hamano, Jul 24, 2024
  2. Eric SunshineJul 24, 2024
  3. Patrick SteinhardtJul 25, 2024
  4. Derrick StoleeJul 25, 2024
  5. Patrick SteinhardtJul 25, 2024
  6. ReviewingGuidelines: encourage positive reviews moreJunio C Hamano, Jul 25, 2024
  7. Patrick SteinhardtJul 26, 2024
  8. Junio C HamanoJul 26, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.