From: Junio C Hamano <gitster@pobox.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: git@vger.kernel.org
Subject: Re: Supporting --depth when cloning from a bundle
Date: Thu, 17 Feb 2022 13:05:55 -0800 [thread overview]
Message-ID: <xmqq7d9t8aq4.fsf@gitster.g> (raw)
In-Reply-To: 20220217141910.oaa6i4lvnotrbecq@meerkat.local
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> Sorry for the potentially stupid follow-up question. I know that git makes a
> distinction when cloning locally between a direct path and a file:// URL (e.g.
> it's only possible to do a shallow clone from a local repository when using
> the file:// scheme).
The local optimization uses hardlinks into an existing repository
bypassing most of what makes Git Git, and there is no negotiation.
"clone --no-local $PATH" or "clone file://$PATH" runs the "server
side" inside $PATH and talks with it, which is ONLY possible because
$PATH is a real repository. A bundle file is not a repository, and
nobody has written the "server side" to workin inside it, so...
prev parent reply other threads:[~2022-02-17 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 22:07 Supporting --depth when cloning from a bundle Konstantin Ryabitsev
2022-02-16 22:37 ` Junio C Hamano
2022-02-17 14:19 ` Konstantin Ryabitsev
2022-02-17 21:05 ` Junio C Hamano [this message]
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=xmqq7d9t8aq4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.