From: Graham Murray <graham@gmurray.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Is a git based tree going to save me bandwidth and time?
Date: Tue, 03 Aug 2010 13:52:45 +0100 [thread overview]
Message-ID: <874ofbn9ia.fsf@newton.gmurray.org.uk> (raw)
In-Reply-To: <i38d41$oh8$1@dough.gmane.org> (Nikos Chantziaras's message of "Tue, 03 Aug 2010 09:31:38 +0300")
Nikos Chantziaras <realnc@arcor.de> writes:
> Git needs to move much less data around than rsync. It only transfers
> differences, not whole files.
But is uses a *lot* more disk space on the systems as each system
contains the full history.
next prev parent reply other threads:[~2010-08-03 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 5:03 [gentoo-user] Is a git based tree going to save me bandwidth and time? Sebastián Ramírez Magrí
2010-08-03 6:31 ` [gentoo-user] " Nikos Chantziaras
2010-08-03 12:52 ` Graham Murray [this message]
2010-08-03 16:38 ` Florian Philipp
2010-08-03 14:11 ` Michael Schreckenbauer
2010-08-03 16:47 ` Florian Philipp
2010-08-03 18:11 ` [gentoo-user] " Sergei Trofimovich
2010-08-03 19:57 ` [gentoo-user] " Sebastián Ramírez Magrí
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=874ofbn9ia.fsf@newton.gmurray.org.uk \
--to=graham@gmurray.org.uk \
--cc=gentoo-user@lists.gentoo.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