From: Shourya Shukla <shouryashukla.oo@gmail.com>
To: Elijah Newren <newren@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com, sandals@crustytoothpaste.net
Subject: Re: [PATCH v4 3/4] gitfaq: shallow cloning a repository
Date: Sat, 2 May 2020 10:30:55 +0530 [thread overview]
Message-ID: <20200502050055.GA5582@konoha> (raw)
In-Reply-To: <CABPp-BG2zf8w6ouK3nn8bid_HKWh2g6Gu-UB65q3Z9V2D80X7A@mail.gmail.com>
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 :)
next prev parent reply other threads:[~2020-05-02 5:01 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 [this message]
2020-04-29 17:09 ` Junio C Hamano
2020-05-02 6:13 ` Shourya Shukla
2020-05-04 16:06 ` Junio C Hamano
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=20200502050055.GA5582@konoha \
--to=shouryashukla.oo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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).