Subject: Re: [PATCH v4 3/4] gitfaq: shallow cloning a repository

From: Shourya Shukla <[email-masked]>
Date: Sat, 2 May 2020 10:30:55 +0530

On 29/04 09:00, Elijah Newren wrote:
> > diff --git a/Documentation/gitfaq.txt b/Documentation/gitfaq.txt
> > index 7d294306f9..6f32846e3d 100644
> > --- a/Documentation/gitfaq.txt
> > +++ b/Documentation/gitfaq.txt
> > @@ -243,6 +243,16 @@ I want to change the remote of my repository. How do I do that?::
> >  One can list the remotes of a repository using `git remote -v` command.
> >  The default name of a remote is 'origin'.
> >
> > +[[shallow-cloning]]
> 
> Why is this marked as "shallow-cloning"?

I forgot to change the heading, will fix it right away.

> > +The repository I am trying to clone is too big. Is there an alternative
> > +way of cloning it in lesser space?::
> > +       A good way to save up space when cloning a repository is
> 
> "save space" instead of "save up space"?

Sure.

> > +       by using `partial clones`. A partial clone will clone the
> > +       full history of the repository but will skip out the entities
> > +       specified by the `--filter` option one uses in `git clone`.
> > +       Any entity which has not been cloned to save space can be cloned
> > +       on-demand. See linkgit:partial-clone[1].
> > +
> 
> I like this much better than suggesting shallow clones, though you
> should mention that partial clones (currently?) presume that you have
> an always-on network connection to the original repository because
> subsequent commands may need to fetch additional objects in order to
> complete.

Alright, I will add that. Thank you for the review :)