From: Enrico Weigelt <weigelt@metux.de>
To: git@vger.kernel.org
Subject: Incremental push w/o compression
Date: Thu, 28 Oct 2010 02:22:26 +0200 [thread overview]
Message-ID: <20101028002224.GA6335@nibiru.local> (raw)
Hi folks,
as discussed in earlier threads, I'm using git for backups on an
machine with quite low memory. Committing works fine now, but
pushing still makes trouble: it takes way too long for compressing.
Is there a way do disable delta compression and transfer the
objects (at least the larger ones) separately (so they're already
on the remote and dont have to be re-transmitted in next pass,
even when the refs have not yet been updated) ?
BTW: what really happens when I push another ref, which has mostly
the same objects, but a different history ? Will the already
present objects be reused or are they all transfered a second time ?
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
----------------------------------------------------------------------
reply other threads:[~2010-10-28 0:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20101028002224.GA6335@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).