From: Junio C Hamano <gitster@pobox.com>
To: David Turner <David.Turner@twosigma.com>
Cc: "Martin Ågren" <martin.agren@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] clarify documentation for remote helpers
Date: Fri, 30 Aug 2019 12:27:53 -0700 [thread overview]
Message-ID: <xmqqimqexxl2.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <c6c737c6a37c4cf7aa77e5c5ffd7a86f@exmbdft7.ad.twosigma.com> (David Turner's message of "Fri, 30 Aug 2019 17:45:43 +0000")
David Turner <David.Turner@twosigma.com> writes:
> The only other restriction I see is: in order for the connectivity-skipping
> optimization to be used, the file with s/.keep/.idx/, and the corresponding
> pack, must exist. Do you think that's worth mentioning? It seems to be
> implied by the rest of the text.
Perhaps if you come up with a way to clarify what is merely implied
(e.g. "this is a mechanism to name a <pack,idx,keep> tuple by
giving only the keep component to do X"), I would imaging that would
be ideal.
Thanks.
prev parent reply other threads:[~2019-08-30 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 21:03 [PATCH] clarify documentation for remote helpers David Turner
2019-08-30 4:03 ` Martin Ågren
2019-08-30 13:47 ` David Turner
2019-08-30 17:34 ` Junio C Hamano
2019-08-30 17:45 ` David Turner
2019-08-30 19:27 ` Junio C Hamano [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqimqexxl2.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=David.Turner@twosigma.com \
--cc=git@vger.kernel.org \
--cc=martin.agren@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.