From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Teng Long via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Teng Long <dyroneteng@gmail.com>
Subject: Re: [PATCH v2 0/3] clone: document partial clone section
Date: Tue, 14 Apr 2020 09:43:42 -0400 [thread overview]
Message-ID: <e77309ef-68a4-0ebd-0d82-051b07838fd5@gmail.com> (raw)
In-Reply-To: <xmqqd08batub.fsf@gitster.c.googlers.com>
On 4/13/2020 6:45 PM, Junio C Hamano wrote:
> "Teng Long via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
>> Partial clones are created using 'git clone', but there is no related help
>> information in the git-clone documentation during a period. Add a relevant
>> section to help users understand what partial clones are and how they differ
>> from normal clones.
>>
>> The section briefly introduces the applicable scenarios and some precautions
>> of partial clone. If users want to know more about its technical design and
>> other details, users can view the link of git-partial-clone(7) according to
>> the guidelines in the section.
>>
>> Derrick Stolee (2):
>> partial-clone: set default filter with --partial
>> clone: document --partial and --filter options
>>
>> Dyrone Teng (1):
>> clone: document partial clone section
>
>> base-commit: 6c85aac65fb455af85745130ce35ddae4678db84
>> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-745%2Fdyrone%2Fmaster-v2
>> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-745/dyrone/master-v2
>> Pull-Request: https://github.com/git/git/pull/745
>>
>> Range-diff vs v1:
>
> Can you remind readers which thread was the v1? Hopefully it is not
> this one, right?
>
> https://lore.kernel.org/git/20200322192234.GC671552@coredump.intra.peff.net/
>
> it concluded that it is not a great idea to set default filter with
> "--partial", and the discussion led to a v2 with a reduced scope at
>
> https://lore.kernel.org/git/pull.586.v2.git.1584906606469.gitgitgadget@gmail.com/
>
> and that one is already cooking.
Yes, sorry about that. I started working with Dyrone on this
when my v1 was still being reviewed, so his commits are based
on that branch. Then when I force-pushed my branch his GGG PR
"grew" with the old commits.
Thanks,
-Stolee
next prev parent reply other threads:[~2020-04-14 13:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 2:02 [PATCH] clone: document partial clone section Teng Long via GitGitGadget
2020-04-02 11:29 ` Derrick Stolee
2020-04-02 17:37 ` Junio C Hamano
2020-04-02 17:52 ` Derrick Stolee
2020-04-13 15:25 ` [PATCH v2 0/3] " Teng Long via GitGitGadget
2020-04-13 15:25 ` [PATCH v2 1/3] partial-clone: set default filter with --partial Derrick Stolee via GitGitGadget
2020-04-13 15:25 ` [PATCH v2 2/3] clone: document --partial and --filter options Derrick Stolee via GitGitGadget
2020-04-13 15:26 ` [PATCH v2 3/3] clone: document partial clone section Dyrone Teng via GitGitGadget
2020-10-27 13:41 ` Philippe Blain
2020-04-13 22:45 ` [PATCH v2 0/3] " Junio C Hamano
2020-04-14 13:43 ` Derrick Stolee [this message]
2020-04-14 16:25 ` Junio C Hamano
2020-04-14 16:26 ` Derrick Stolee
2020-04-14 13:42 ` Derrick Stolee
2020-10-27 3:12 ` [PATCH v3] " Teng Long via GitGitGadget
2020-10-27 13:13 ` Philippe Blain
2020-10-27 18:51 ` Junio C Hamano
2021-02-25 9:13 ` [PATCH v4] " Teng Long via GitGitGadget
2021-02-25 13:38 ` Philippe Blain
2021-03-02 14:25 ` [PATCH v5] " Teng Long via GitGitGadget
2021-03-03 19:25 ` Junio C Hamano
2021-05-06 6:27 ` Fix inconsistent signed-off-by abd author name Teng Long
2021-05-06 6:30 ` [PATCH 1/1] clone: document partial clone section Teng Long
2021-05-07 4:00 ` Bagas Sanjaya
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=e77309ef-68a4-0ebd-0d82-051b07838fd5@gmail.com \
--to=stolee@gmail.com \
--cc=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.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).