From: Petr Baudis <pasky@suse.cz>
To: Pavel Roskin <proski@gnu.org>
Cc: git <git@vger.kernel.org>
Subject: Re: cg-pull to pull branches, not the whole repository
Date: Thu, 15 Sep 2005 01:34:12 +0200 [thread overview]
Message-ID: <20050914233412.GG2936@pasky.or.cz> (raw)
In-Reply-To: <1126733516.10827.54.camel@dv>
Dear diary, on Wed, Sep 14, 2005 at 11:31:56PM CEST, I got a letter
where Pavel Roskin <proski@gnu.org> told me that...
> Hello!
Hello,
> I believe cg-pull should be changed to pull only the objects relevant to
> the branch rather than the whole repository.
well, that should be the case for all the methods but rsync. Actually,
it's not the case for local pulls now either, because git-local-pull
wasn't able to deal with packs, but I think that's fixed by now so I'll
reenable that.
> Ideally, cogito should not rely on the server being able to list
> directories. This would allow support more protocols and servers, e.g.
> http servers without directory listings. Unfortunately, listings are
> still needed to get refs/tags and refs/heads. Any fix for that would
> involve git core, and I don't see an elegant fix.
Well, there's that update-server-info thing. It'd be nice if
git-send-pack could call that automagically or something, so it's kept
up-to-date. But I have no idea about how expensive can the command
actually be.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone. -- Alan Cox
prev parent reply other threads:[~2005-09-14 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 21:31 cg-pull to pull branches, not the whole repository Pavel Roskin
2005-09-14 22:05 ` Junio C Hamano
2005-09-16 3:09 ` Pavel Roskin
2005-09-14 23:34 ` Petr Baudis [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=20050914233412.GG2936@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=proski@gnu.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).