From: Elijah Newren <newren@gmail.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
"Nguyễn Thái Ngọc" <pclouds@gmail.com>,
git@vger.kernel.org
Subject: Re: Configurable callbacks for missing objects (we Re: upload-pack: support subtree packing)
Date: Tue, 27 Jul 2010 19:53:59 -0600 [thread overview]
Message-ID: <AANLkTimrp4z0n75Zq7BtTvdWz6nzK3M4J9ohdbE6X3t3@mail.gmail.com> (raw)
In-Reply-To: <20100727185127.GD25124@worldvisions.ca>
2010/7/27 Avery Pennarun <apenwarr@gmail.com>:
> But I've been thinking that a really elegant way to solve the problem could
> be to have a user-configurable "get the missing objects" callback. If any
> part of git that *needs* an object can't find it, it calls this callback to
> go try to retrieve it (either just that one object, or it can request to
> download the object recursively, ie. everything it points to).
>
> Then shallow clones could just auto-fill themselves if you really need a
> prior version, for example.
What counts as "needing" an object? Does 'git log -Sfoo' or 'git log
--stat' need all missing blobs? I'd personally dislike having such
commands automatically result in huge downloads, but I'd probably
dislike the automatic downloading in general so perhaps I'm just a
misfit for the lazy clone usecase. It's still an interesting question
though -- what counts as needed?
next prev parent reply other threads:[~2010-07-28 1:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 23:36 [PATCH 0/2] Subtree clone? Nguyễn Thái Ngọc Duy
2010-07-26 23:36 ` [PATCH 1/2] upload-pack: support subtree packing Nguyễn Thái Ngọc Duy
2010-07-27 13:15 ` Ævar Arnfjörð Bjarmason
2010-07-27 14:46 ` Shawn O. Pearce
2010-07-27 18:51 ` Configurable callbacks for missing objects (we Re: upload-pack: support subtree packing) Avery Pennarun
2010-07-27 22:32 ` Nguyen Thai Ngoc Duy
2010-07-28 1:53 ` Elijah Newren [this message]
2010-07-28 2:00 ` Avery Pennarun
2010-07-27 22:29 ` [PATCH 1/2] upload-pack: support subtree packing Nguyen Thai Ngoc Duy
2010-07-26 23:36 ` [PATCH 2/2] fetch-pack: support --subtree and --commit-subtree options Nguyễn Thái Ngọc Duy
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=AANLkTimrp4z0n75Zq7BtTvdWz6nzK3M4J9ohdbE6X3t3@mail.gmail.com \
--to=newren@gmail.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=spearce@spearce.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 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).