From: sebasmagri@gmail.com (Sebastián Ramírez Magrí)
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Is a git based tree going to save me bandwidth and time?
Date: Tue, 03 Aug 2010 00:33:42 -0430 [thread overview]
Message-ID: <87pqy02spd.fsf@gmail.com> (raw)
Hi folks...
I've been thinking about switching from a rsync based tree to a git
based one cloning [0]. The main reasons because I would do that is in
order to save bandwidth (I've a slow GSM connection in my netbook and
I sync two other gentoo boxes from the first one) and maybe time.
So here goes the question, Is a git based tree really going to save me
an appreciable bandwidth and time on syncing?, Can I keep the same
replication functionality rsync gives me to sync my other boxes?
[0] http://github.com/funtoo/portage/tree/gentoo.org
next reply other threads:[~2010-08-03 5:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 5:03 Sebastián Ramírez Magrí [this message]
2010-08-03 6:31 ` [gentoo-user] Re: Is a git based tree going to save me bandwidth and time? Nikos Chantziaras
2010-08-03 12:52 ` Graham Murray
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=87pqy02spd.fsf@gmail.com \
--to=sebasmagri@gmail.com \
--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