From: Jakub Narebski <jnareb@gmail•com>
To: git@vger•kernel.org
Subject: Re: Remote git-cat-file?
Date: Sun, 28 May 2006 20:34:43 +0200 [thread overview]
Message-ID: <e5cqg5$om2$1@sea.gmane.org> (raw)
In-Reply-To: 7vu07acanv.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail•com> writes:
>
>> It would be nice I think to be able to have remote alternatives,...
>
> Yup, I think I've mentioned that one as one of "the mostly
> unimplementable but would be very nice to have crazy wishlist
> items" some time ago. What people would want is not a "shallow"
> clone, but a "lazy" clone, and in the ideal world that would
> obviously be a nice thing to have.
I think that it should be only "commit-lazy", i.e. downloading whole trees,
subtrees, and objects pointed by tags, only not following the parent links
of commits; perhaps also other links to commits (branches, tags, tag
objects).
--
Jakub Narebski
Warsaw, Poland
prev parent reply other threads:[~2006-05-28 18:35 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
2006-05-28 17:38 ` Junio C Hamano
2006-05-28 18:34 ` Jakub Narebski [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='e5cqg5$om2$1@sea.gmane.org' \
--to=jnareb@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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