On Sun, May 3, 2020 at 10:42 PM Shourya Shukla <shouryashukla.oo@xxxxxxxxx> wrote: > Subject: [PATCH v5 3/4] gitfaq: shallow cloning a repository Shouldn't the subject be updated as well, since we're talking about partial clones rather than shallow clones? > Add issue in 'Common issue' section which covers issues with cloning > large repositories. Use partial cloning to selectively clone the > repository. > > Signed-off-by: Shourya Shukla <shouryashukla.oo@xxxxxxxxx> > --- > I fixed the heading of this section and improved it overall though, > as pointed out by Junio, there is a bit confusion as to what URL I > am trying to point to: > https://git-scm.com/docs/partial-clone > This is the URL I want to point to. > > Documentation/gitfaq.txt | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/Documentation/gitfaq.txt b/Documentation/gitfaq.txt > index 875cfa0acd..5dfbb32089 100644 > --- a/Documentation/gitfaq.txt > +++ b/Documentation/gitfaq.txt > @@ -244,6 +244,17 @@ 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'. > > +[[partial-cloning]] > +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 space when cloning a repository is 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 (hence this > + presumes that the user has an always-on network connection to the > + original repository). See linkgit:partial-clone[1]. > + > Hooks > ----- > > -- > 2.26.2 >
