From: Avery Pennarun <apenwarr@gmail.com>
To: Joe Brenner <doom@kzsu.stanford.edu>
Cc: Noah Silverman <noah@smartmediacorp.com>, git@vger.kernel.org
Subject: Re: Advice on choosing git
Date: Wed, 12 May 2010 20:31:32 -0400 [thread overview]
Message-ID: <AANLkTikc6_jZoMzF1VhfJBSk1DRHCNNP3puPT0Z2Usk5@mail.gmail.com> (raw)
In-Reply-To: <201005130018.o4D0I7iI079145@kzsu.stanford.edu>
On Wed, May 12, 2010 at 8:18 PM, Joe Brenner <doom@kzsu.stanford.edu> wrote:
> Noah Silverman <noah@smartmediacorp.com> wrote:
>> 1) Size. THIS IS MY MAIN CONCERN - If I want to sync my home, office,
>> and server Document directories. From what I have read, I will
>> effectively have multiple copies of each item on my hard drive, thus
>> eating up a lot of space
>
> Pretty much any version control system is going to have this problem,
> and it gets really bad if you've got any files that aren't straight text.
Note that most people probably don't need to worry about this
nowadays. Disk $/gigabyte just keeps dropping and is now at
absolutely abysmally small levels. You can only fill up your disks if
you download tons of movies and/or create tons of VMs.
If you're struggling with a laptop drive that's too small, just buy a
new one for $100 and solve all your problems.
So you're fine with storing multiple copies. Just make sure your
backup/syncing software has an expiration algorithm so you don't end
up storing *all* the historical copies.
I'd like to adapt bup to support this usage model eventually.
However, I haven't yet written the expiration algorithm and it doesn't
yet support two-way syncing. The fundamental design allows for this,
though, so it's just a matter of having some free time. Meanwhile,
you might want to take a look at something like rdiff-backup.
Have fun,
Avery
next prev parent reply other threads:[~2010-05-13 0:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 6:31 Advice on choosing git Noah Silverman
2010-05-12 9:04 ` Dmitry Potapov
2010-05-12 9:15 ` Ramkumar Ramachandra
2010-05-12 9:24 ` Jonathan Nieder
2010-05-13 0:18 ` Joe Brenner
2010-05-13 0:31 ` Avery Pennarun [this message]
2010-05-13 11:48 ` Matthieu Moy
2010-05-13 17:31 ` Avery Pennarun
2010-05-19 0:37 ` Anthony W. Youngman
2010-05-19 1:12 ` Avery Pennarun
2010-05-13 11:42 ` Matthieu Moy
2010-05-13 11:51 ` Jeff King
2010-05-13 18:20 ` Martin Langhoff
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=AANLkTikc6_jZoMzF1VhfJBSk1DRHCNNP3puPT0Z2Usk5@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=doom@kzsu.stanford.edu \
--cc=git@vger.kernel.org \
--cc=noah@smartmediacorp.com \
/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).