git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Supporting --depth when cloning from a bundle
Date: Thu, 17 Feb 2022 09:19:10 -0500	[thread overview]
Message-ID: <20220217141910.oaa6i4lvnotrbecq@meerkat.local> (raw)
In-Reply-To: <xmqqzgmqbfq7.fsf@gitster.g>

On Wed, Feb 16, 2022 at 02:37:20PM -0800, Junio C Hamano wrote:
> The "depth" is used to negitiate what objects to include in the
> packfile that is transmit from the other side.  That would not
> fundamentally work on bundles, because a bundle is pregenerated and
> there is nobody on the other side for you to negotiate with to
> affect what objects are included in the packfile which is contained
> in the bundle file.

Junio:

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). When that happens, doesn't that same negotiation happen
locally (perhaps in a simulated way)? If that so, then theoretically the same
approach could be taken with the bundle file?

(I'm not actually that interested in that feature, to be honest -- I'd much
rather see further work on git-native CDN offload of packfiles, so we stop
using kludges like bundle files for this purpose.)

-K

  reply	other threads:[~2022-02-17 14:19 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 [this message]
2022-02-17 21:05     ` 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=20220217141910.oaa6i4lvnotrbecq@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).