git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: 滕龙 <dyroneteng@gmail.com>
Cc: Git mailing list <git@vger.kernel.org>
Subject: Re: Help for the git patch with "---"
Date: Thu, 25 Feb 2021 08:14:38 -0500	[thread overview]
Message-ID: <25082af3-e8fd-e9d6-e980-43871c5b4840@gmail.com> (raw)
In-Reply-To: <CADMgQSR8cOJs_XGuArqRoRxes6RxxgitMvDFYhpYVGxg6A2VZQ@mail.gmail.com>

Hi Dyrone,

[CC-ing the list]

Le 2021-02-25 à 04:36, 滕龙 a écrit :
> Oh, I reviewed the PR ((link: https://github.com/git/git/pull/745 <https://github.com/git/git/pull/745>)),  maybe I got the point of it.
> 
> It's caused by the first comment I leave on the PR,  so every new patch will attach it to the maillist.

Exactly. The first comment on the PR (the PR description) is used
as a cover letter for multi-patch series, and in the case of one-patch
series like yours is now, it is inserted as an "in-patch commentary", i.e.
it is added below the '---' line as you found out.

> 
> I decide to remove it from the PR.
> 
> So, did I deal the right way this time?

Well, if you are sending a subsequent version of your patch series,
this space is usually used to summarize in words what
has changed since the last version of the patch series.
For example, for your v4 you could have written:

Changes since v3:
- Improved <that> following comment from <insert reviewer name>
- Reworded the commit message
- etc.

This is a explained in the MyFirstContribution tutorial [1]. I would
encourage you to do that if your series needs a v5 (I haven't read it yet).
It's also a way to make sure that you modified your patch to account
for all feedback you got in earlier iterations.

> 
> Thank you
> 
> -dyrone
> 

One last thing: most people prefer not to be emailed directy, but instead
to be CC-ed on an email you send to the mailing list (git@vger.kernel.org).
You have much better chance of receiving an answer this way, as anybody who
reads the mailing list will see your message and might take the time to answer.

Cheers,

Philippe.


[1] https://git-scm.com/docs/MyFirstContribution#responding-ggg

       reply	other threads:[~2021-02-25 13:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADMgQST4wSH+bt5auGuO6KYoQzyrkhnY2RY4Q1jGLVczGrMG+Q@mail.gmail.com>
     [not found] ` <CADMgQSR8cOJs_XGuArqRoRxes6RxxgitMvDFYhpYVGxg6A2VZQ@mail.gmail.com>
2021-02-25 13:14   ` Philippe Blain [this message]
2021-02-25 13:22     ` Help for the git patch with "---" Philippe Blain

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=25082af3-e8fd-e9d6-e980-43871c5b4840@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=dyroneteng@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).