git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Atharva Raykar <raykar.ath@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Git List <git@vger.kernel.org>,
	Christian Couder <christian.couder@gmail.com>,
	Shourya Shukla <periperidip@gmail.com>,
	Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Subject: Re: My Git Dev Blog - Week 9
Date: Mon, 19 Jul 2021 14:23:29 +0530	[thread overview]
Message-ID: <E8CA36A6-2FC0-4A76-9461-D5F4CA205AB8@gmail.com> (raw)
In-Reply-To: <fcb14e9b-c76d-9a54-fccb-d66e7de04f7a@gmail.com>

On 19-Jul-2021, at 06:21, Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> 
> 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


      reply	other threads:[~2021-07-19  9:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-18 11:59 My Git Dev Blog - Week 9 Atharva Raykar
2021-07-18 13:15 ` Christian Couder
2021-07-19  8:57   ` Atharva Raykar
2021-07-18 19:19 ` Kaartic Sivaraam
2021-07-19  2:58   ` Kaartic Sivaraam
2021-07-19  8:48     ` Atharva Raykar
2021-07-19  0:51 ` Bagas Sanjaya
2021-07-19  8:53   ` Atharva Raykar [this message]

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=E8CA36A6-2FC0-4A76-9461-D5F4CA205AB8@gmail.com \
    --to=raykar.ath@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=periperidip@gmail.com \
    /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).