From: Enrico Weigelt <weigelt@metux.de>
To: git@vger.kernel.org
Subject: incremental push/pull for large repositories
Date: Sat, 10 Jul 2010 05:12:59 +0200 [thread overview]
Message-ID: <20100710031258.GA554@nibiru.local> (raw)
Hi folks,
I often have situations where I've rebased branches with large files
(10th of megabytes per file) and pushing them to the remote. Normally
these files themselves stay untouched, but the history changes (eg.
commits reordered, several changes in smaller files,etc).
It seem that on each push, the whole branch is transferred, including
all the large files, which already exist on the remote site. Is there
any way to prevent this ?
IMHO it would be enough having a negotiation on which objects really
have to be transferred before creating and transmitting the actual
pack file. That would save _much_ traffic (and transmit time) for
those situations.
This could also be used to remotely repair broken repositories:
just repack leaving off the broken objects and fetch the missing
ones from remotes.
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
next reply other threads:[~2010-07-10 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-10 3:12 Enrico Weigelt [this message]
2010-07-12 15:17 ` incremental push/pull for large repositories Avery Pennarun
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=20100710031258.GA554@nibiru.local \
--to=weigelt@metux.de \
--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).