git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Teng Long <dyroneteng@gmail.com>
To: gitster@pobox.com
Cc: dyroneteng@gmail.com, git@vger.kernel.org, jonathantanmy@google.com
Subject: Re: [PATCH v2] packfile-uri.txt: fix blobPackfileUri description
Date: Thu, 13 May 2021 14:44:45 +0800	[thread overview]
Message-ID: <CADMgQSR=f0kAnX0Fat2vSpVaG62WX9VAkU0xNeN_hiDaHXu-eA@mail.gmail.com> (raw)

Junio C Hamano writes:

>Yes.  Some people seem to omit the final response to reviewer
>suggestions on the previous round and just send a revised patch, but
>it is much nicer to cleanly conclude the review cycle for the
>previous round with a separate response (it could just be "yes,
>you're right---I'll incorporate your suggestions in the next round,
>thanks") before starting a new cycle.

If I  send a new patch cycle, the "--thread"  argument seems
to be recommended. This may be the reason why it is easier
to understand when submitting a series of patches?

I may try to use "--thread", but it may make this whole
patch more confusing, sorry for that.

             reply	other threads:[~2021-05-13  6:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13  6:44 Teng Long [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-06 21:39 [PATCH] Optimize the description of the configuration in packfile-uris doc Junio C Hamano
2021-05-11  6:45 ` [PATCH v2] packfile-uri.txt: fix blobPackfileUri description Teng Long
2021-05-11 20:50   ` Junio C Hamano
2021-05-12 14:10     ` Long Teng
2021-05-12 23:32       ` Junio C Hamano

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='CADMgQSR=f0kAnX0Fat2vSpVaG62WX9VAkU0xNeN_hiDaHXu-eA@mail.gmail.com' \
    --to=dyroneteng@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jonathantanmy@google.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.
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).