From: Junio C Hamano <gitster@pobox.com>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: "'Shourya Shukla'" <shouryashukla.oo@gmail.com>,
<git@vger.kernel.org>, <sandals@crustytoothpaste.net>,
"'Derrick Stolee'" <dstolee@microsoft.com>,
"'Elijah Newren'" <newren@gmail.com>,
"'Christian Couder'" <christian.couder@gmail.com>
Subject: Re: [PATCH v3 3/4] gitfaq: shallow cloning a repository
Date: Tue, 21 Apr 2020 13:57:49 -0700 [thread overview]
Message-ID: <xmqq1rogmu9e.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <011001d6181d$97301fc0$c5905f40$@nexbridge.com> (Randall S. Becker's message of "Tue, 21 Apr 2020 16:43:55 -0400")
"Randall S. Becker" <rsbecker@nexbridge.com> writes:
>> 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).
>
> I rather hate to chime in as a dissenting opinion,...
Oh, don't hate anything. It is greatly appreciated so that we can
cover "in such and such use case, this solution is good" variants
for similarly-sounding-but-fundamentally-different classes of
problems. We do not want to give a spinal-reflex answer of "use
shallow" (or "use partial", for that matter) to "too large a repo"
question without contexts that guide the readers to a better choice.
That is where a well-organized FAQ list shines.
Thanks.
next prev parent reply other threads:[~2020-04-21 20:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 13:12 [PATCH v3 0/4] gitfaq: add issues in the 'Common Issues' section Shourya Shukla
2020-04-21 13:12 ` [PATCH v3 1/4] gitfaq: files in .gitignore are tracked Shourya Shukla
2020-04-21 19:45 ` Junio C Hamano
2020-04-21 13:12 ` [PATCH v3 2/4] gitfaq: changing the remote of a repository Shourya Shukla
2020-04-21 19:54 ` Junio C Hamano
2020-04-27 17:30 ` Shourya Shukla
2020-04-21 13:12 ` [PATCH v3 3/4] gitfaq: shallow cloning " Shourya Shukla
2020-04-21 20:00 ` Junio C Hamano
2020-04-21 20:43 ` Randall S. Becker
2020-04-21 20:57 ` Junio C Hamano [this message]
2020-04-21 21:25 ` Randall S. Becker
2020-04-22 1:30 ` Derrick Stolee
2020-04-22 4:00 ` Jonathan Nieder
2020-04-22 0:13 ` Elijah Newren
2020-04-21 13:12 ` [PATCH v3 4/4] gitfaq: fetching and pulling " Shourya Shukla
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1rogmu9e.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=rsbecker@nexbridge.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.
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 NNTP newsgroup(s).