From: Avery Pennarun <apenwarr@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: turner25@gmail.com, git@vger.kernel.org
Subject: Re: git as backup and file sync system
Date: Fri, 2 Apr 2010 15:49:53 -0400 [thread overview]
Message-ID: <j2v32541b131004021249s738a06cfq2804b97f798ac482@mail.gmail.com> (raw)
In-Reply-To: <k2mfabb9a1e1004021235xc75e25a8na941c1754fd543c@mail.gmail.com>
On Fri, Apr 2, 2010 at 3:35 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> On Fri, Apr 2, 2010 at 13:16, Simon <turner25@gmail.com> wrote:
>> I'm not sure if this post will be very welcome, but I'd like your
>> feedback or suggestions. I've been reading Jon Loeliger's book about
>> git and I've understood many many things. I'm interested in using git
>> as a backup and sync system between computers.
>
> You might want to look into 'bup', [0] designed specifically for that
> purpose. It seems like introduction post about it on apenwarr.ca is
> down though [1].
>
> [0] http://github.com/apenwarr/bup
> [1] http://apenwarr.ca/log/?m=201001#04
Yeah, sorry, apenwarr.ca is flakey at the best of times. It takes after me :)
Disclaimer: bup does lots of neat backup-related stuff, but it doesn't
*yet* support detailed metadata. We're working on it:
http://groups.google.com/group/bup-list/browse_thread/thread/e899a579a6f7ae55
If you're only storing a relatively small number of files (say /etc),
then something like etckeeper might do what you want. Or more
generally, metastore (which etckeeper uses):
http://david.hardeman.nu/software.php
Unfortunately neither git nor metastore can handle the high data
volumes that bup is aimed at (ie. your entire filesystem, including
huge files), which is why bup exists. Give it a few weeks and we
should have some decent metadata handling in place though.
Have fun,
Avery
next prev parent reply other threads:[~2010-04-02 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 19:16 git as backup and file sync system Simon
2010-04-02 19:35 ` Sverre Rabbelier
2010-04-02 19:49 ` Avery Pennarun [this message]
2010-04-02 21:20 ` Simon
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=j2v32541b131004021249s738a06cfq2804b97f798ac482@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.com \
--cc=turner25@gmail.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).