From: Junio C Hamano Date: Tue, 21 Apr 2020 20:00:42 GMT Subject: Re: [PATCH v3 3/4] gitfaq: shallow cloning a repository Message-ID: In-Reply-To: <20200421131223.29337-4-shouryashukla.oo@gmail.com> Shourya Shukla writes: > Add issue in 'Common issue' section which covers issues with cloning > large repositories. Use shallow cloning to clone the repository in > a smaller size. > > Signed-off-by: Shourya Shukla > --- > Documentation/gitfaq.txt | 14 ++++++++++++++ > 1 file changed, 14 insertions(+) > > diff --git a/Documentation/gitfaq.txt b/Documentation/gitfaq.txt > index 13d37f96af..cea293cf07 100644 > --- a/Documentation/gitfaq.txt > +++ b/Documentation/gitfaq.txt > @@ -275,6 +275,20 @@ 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]] > +The repository I am trying to clone is too big. Is there an alternative > +way of cloning it in lesser space?:: > + One can clone a repository having a truncated history, meaning the > + history will span upto a specified number of commits instead of > + the whole history of the repository. This is called 'Shallow Cloning'. > ... The question is worth keeping but the answer is questionable. I have a feeling that --depth/shallow is deprecated/frowned upon these days and more people recommend partial/blob-less clones instead (a few random people added to Cc: to see if they want to say something here).