From: Simon <turner25@gmail.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>, git@vger.kernel.org
Subject: Re: git as backup and file sync system
Date: Fri, 2 Apr 2010 17:20:20 -0400 [thread overview]
Message-ID: <v2l5f14cf5e1004021420mcd67bb5bh23730ae53f2aa8c6@mail.gmail.com> (raw)
In-Reply-To: <j2v32541b131004021249s738a06cfq2804b97f798ac482@mail.gmail.com>
Hey thanks guys!
This looks cool, I mean, I don't really care that it doesn't support
everything topshape, I'm sure I can manage something with this. I'll
clearly look into it. What I like most is that development on it is
alive now. =)
Simon
On Fri, Apr 2, 2010 at 3:49 PM, Avery Pennarun <apenwarr@gmail.com> wrote:
> 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
>
prev parent reply other threads:[~2010-04-02 21:20 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
2010-04-02 21:20 ` Simon [this message]
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=v2l5f14cf5e1004021420mcd67bb5bh23730ae53f2aa8c6@mail.gmail.com \
--to=turner25@gmail.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@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).