From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Jonathan Tan <jonathantanmy@google.com>,
stolee@gmail.com, git@vger.kernel.org,
christian.couder@gmail.com
Subject: Re: [Question] Is extensions.partialClone defunct?
Date: Thu, 12 Mar 2020 14:17:40 -0700 [thread overview]
Message-ID: <xmqqsgide0i3.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200312210954.GA13644@syl.local> (Taylor Blau's message of "Thu, 12 Mar 2020 15:09:54 -0600")
Taylor Blau <me@ttaylorr.com> writes:
> On Thu, Mar 12, 2020 at 10:51:51AM -0700, Jonathan Nieder wrote:
>> Jonathan Tan wrote:
>> > Derrick Stolee wrote:
>>
>> >> but it appears that we rely on the "remote.<name>.promisor = true"
>> >> setting instead of this extension.
>> >
>> > Hmm...besides giving the name of the promisor remote, the
>> > extensions.partialClone setting is there to prevent old versions of Git
>> > (that do not know this extension) from manipulating the repo.
>
> Manipulating it how?
Presumably if the version of Git does not assume that sometimes
missing objects are OK, its "fsck" and "repack" would become very
upset when a repository lacks very many objects because the version
of Git that created it assumes they can be lazily fetched, no?
next prev parent reply other threads:[~2020-03-12 21:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 12:23 [Question] Is extensions.partialClone defunct? Derrick Stolee
2020-03-12 17:07 ` Jonathan Tan
2020-03-12 17:51 ` Jonathan Nieder
2020-03-12 18:10 ` Junio C Hamano
2020-03-12 21:09 ` Taylor Blau
2020-03-12 21:17 ` Junio C Hamano [this message]
2020-03-12 21:30 ` Jeff King
2020-03-12 21:54 ` Christian Couder
2020-03-12 21:59 ` Christian Couder
2020-03-12 23:09 ` Jonathan Nieder
2020-03-14 6:43 ` Christian Couder
2021-06-05 13:01 ` Tao Klerks
2020-03-13 0:10 ` 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=xmqqsgide0i3.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=me@ttaylorr.com \
--cc=stolee@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.
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).