git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Shourya Shukla <shouryashukla.oo@gmail.com>
Cc: git@vger.kernel.org, newren@gmail.com,
	sandals@crustytoothpaste.net, christian.couder@gmail.com,
	dstolee@microsoft.com, jonathantanmy@google.com
Subject: Re: [PATCH v4 3/4] gitfaq: shallow cloning a repository
Date: Mon, 04 May 2020 09:06:06 -0700	[thread overview]
Message-ID: <xmqqzhanhehd.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200502061355.GB5582@konoha> (Shourya Shukla's message of "Sat, 2 May 2020 11:43:55 +0530")

Shourya Shukla <shouryashukla.oo@gmail.com> writes:

> On 29/04 10:09, Junio C Hamano wrote:
>> > ---
>> > I wanted to ask why is there no mention of partial cloning in
>> > the 'git-clone' documentation? Is it because it is an experimental
>> > feature?
>> 
>> If the folks that have been pushing the feature haven't bothered to
>> document it fully, by definition, it must be a work in progress that
>> is not ready for the prime time ;-)
>> 
>> Jokes aside, the --filter=<filter-spec> option is mentioned in the
>> documentation and it says "...is used for the partial clone filter",
>> without even defining what a "partial clone filter" really is.
>> 
>> The topic deserves its own subsection, between the "Git URLs" and
>> the "Examples" sections, in git-clone(1).
>
> May I try to add it? If yes then are there any points to be kept in mind
> while writing this part (for eg., length of the subsection, writing
> style, what all is to be written etc.)?

I am much less qualified to answer these questions than others on
the CC: list.

Who added the mention to --filter and "used for the partial clone filter"
to the page anyway?  Did you run "git blame" to find out?

    ... goes and looks ...

It was added by 4a465443 (clone: document --filter options, 2020-03-22).

Derrick, perhaps you can help Shourya to find a good place to give
a birds-eye description for the partial-clone feature and figure out
what points about the feature are worth covering there?

Thanks.


  reply	other threads:[~2020-05-04 16:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29  9:38 [PATCH v4 1/4] gitfaq: files in .gitignore are tracked Shourya Shukla
2020-04-29  9:38 ` [PATCH v4 2/4] gitfaq: changing the remote of a repository Shourya Shukla
2020-04-29 16:17   ` Elijah Newren
2020-04-29 17:01   ` Junio C Hamano
2020-04-29  9:38 ` [PATCH v4 3/4] gitfaq: shallow cloning " Shourya Shukla
2020-04-29 16:00   ` Elijah Newren
2020-05-02  5:00     ` Shourya Shukla
2020-04-29 17:09   ` Junio C Hamano
2020-05-02  6:13     ` Shourya Shukla
2020-05-04 16:06       ` Junio C Hamano [this message]
2020-05-05 12:26         ` Derrick Stolee
2021-05-06  2:49           ` dyrone teng
2020-04-29  9:38 ` [PATCH v4 4/4] gitfaq: fetching and pulling " Shourya Shukla
2020-04-29 15:56   ` Elijah Newren
2020-04-29 17:19     ` Junio C Hamano
2020-05-02  6:57     ` Shourya Shukla
2020-05-02 19:00       ` Elijah Newren
2020-05-03  1:03         ` Junio C Hamano
2020-04-29 16:16 ` [PATCH v4 1/4] gitfaq: files in .gitignore are tracked Elijah Newren
2020-05-02  6:36   ` Shourya Shukla
2020-04-29 16:55 ` 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

  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=xmqqzhanhehd.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=dstolee@microsoft.com \
    --cc=git@vger.kernel.org \
    --cc=jonathantanmy@google.com \
    --cc=newren@gmail.com \
    --cc=sandals@crustytoothpaste.net \
    --cc=shouryashukla.oo@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).