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

Re: My Git Dev Blog - Week 9

From
Atharva Raykar <raykar.ath@gmail.com>
Date
Jul 19, 2021, 08:53 UTC
Message-ID
<E8CA36A6-2FC0-4A76-9461-D5F4CA205AB8@gmail.com>
In-Reply-To
<fcb14e9b-c76d-9a54-fccb-d66e7de04f7a@gmail.com>
On 19-Jul-2021, at 06:21, Bagas Sanjaya <bagasdotme@gmail.com> wrote:
Show 9 quoted lines
> 
> On 18/07/21 18.59, Atharva Raykar wrote:
>> Here's my latest blog post:
>> https://atharvaraykar.me/gitnotes/week9
> 
> You wrote:
>> Interact more with the community by asking questions in your patch cover letters and replies to reviews.
> 
> Did you mean something like [RFC PATCH]?

That would be one part of it, but I meant it in a more general sense, ie, it is better to be detailed and specific about design decisions in a patch that one may not be sure of, and mention it up front.

That, and asking questions to reviewers to clarify what they mean, and their motivations behind it, if one is not sure of those.

> -- 
> An old man doll... just what I always wanted! - Clara
Previous: Bagas Sanjaya
Message 8 of 8 in “My Git Dev Blog - Week 9”
  1. Atharva RaykarJul 18, 2021
  2. Christian CouderJul 18, 2021
  3. Atharva RaykarJul 19, 2021
  4. Kaartic SivaraamJul 18, 2021
  5. Kaartic SivaraamJul 19, 2021
  6. Atharva RaykarJul 19, 2021
  7. Bagas SanjayaJul 19, 2021
  8. Atharva RaykarJul 19, 2021

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.