From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Remote git-cat-file?
Date: Sun, 28 May 2006 14:00:21 +0200 [thread overview]
Message-ID: <e5c3c5$i47$1@sea.gmane.org> (raw)
In-Reply-To: loom.20060528T124835-757@post.gmane.org
Elrond wrote:
> Linus Torvalds <torvalds <at> osdl.org> writes:
>>
>> Just out of interest, why would you ever want to just look at a single
>> object?
[...]
>
> The other possible use for remote git-cat-file:
> It might be useful in shallow repos to selectively load objects "on demand".
> (In fact, I screwed my repo by trying to make it shallow.)
It would be nice I think to be able to have remote alternatives, loading
(downloading and saving) objects "on demand" ("lazy alternatives"). Not necessary
only with "shallow repo"/"shallow clone".
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-05-28 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 22:26 Remote git-cat-file? Elrond
2006-05-28 0:29 ` Linus Torvalds
2006-05-28 0:32 ` Linus Torvalds
2006-05-28 10:57 ` Elrond
2006-05-28 12:00 ` Jakub Narebski [this message]
2006-05-28 17:38 ` Junio C Hamano
2006-05-28 18:34 ` Jakub Narebski
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='e5c3c5$i47$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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).