From: Pavel Roskin <proski@gnu.org>
To: Petr Baudis <pasky@suse.cz>
Cc: git <git@vger.kernel.org>
Subject: cg-pull to pull branches, not the whole repository
Date: Wed, 14 Sep 2005 17:31:56 -0400 [thread overview]
Message-ID: <1126733516.10827.54.camel@dv> (raw)
Hello!
I believe cg-pull should be changed to pull only the objects relevant to
the branch rather than the whole repository. This could be more
expensive in terms of processor power (since the objects would be
checked for parents), but it would save the bandwidth, especially for
users tracking stable branches with little changes in presence of
heavily changed development branches in the same repository.
To keep things simple, pulling the whole repository should be removed
from cogito. Users don't need objects that are not reachable from any
branch known to cogito. If I'm not tracking a branch, I don't want
objects from it. To compensate for intermittently connected users,
cg-pull could have an option to pull from all branches (or from all
branches marked for automatic pull).
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.
For git+ssh protocol, git-fetch-pack already provides a server side
solution. Client side support would be needed for http and rsync.
I'd like to hear comments before I attempt any hacking in this
direction.
--
Regards,
Pavel Roskin
next reply other threads:[~2005-09-14 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 21:31 Pavel Roskin [this message]
2005-09-14 22:05 ` cg-pull to pull branches, not the whole repository Junio C Hamano
2005-09-16 3:09 ` Pavel Roskin
2005-09-14 23:34 ` Petr Baudis
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=1126733516.10827.54.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).