From: John Tapsell <johnflux@gmail.com>
To: Roald de Vries <rdv@roalddevries.nl>
Cc: git@vger.kernel.org
Subject: Re: backups with git
Date: Mon, 10 Aug 2009 11:51:13 +0100 [thread overview]
Message-ID: <43d8ce650908100351w10e4d49cne8cff6f7e900f07a@mail.gmail.com> (raw)
In-Reply-To: <41CB836B-6057-448E-805F-F25EAF765D27@roalddevries.nl>
2009/8/10 Roald de Vries <rdv@roalddevries.nl>:
> Dear all,
>
> I'm thinking of using git as a backup solution for my whole system, setting
> my $GIT_DIR to something like "/backupdisc/backup". Does that seem sensible?
> In his Google tech talk, Linus said that git was not good at huge projects;
> I guess that would apply to backups. On the other hand, maybe a backup
> doesn't need to be as fast as he wants git to be for projects. Has anybody
> used git like this? And was it a good experience?
Perhaps you want something more like btrfs.
John
next prev parent reply other threads:[~2009-08-10 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 8:27 backups with git Roald de Vries
2009-08-10 10:51 ` John Tapsell [this message]
2009-08-10 13:20 ` Martin Langhoff
2009-08-10 13:38 ` Sitaram Chamarty
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=43d8ce650908100351w10e4d49cne8cff6f7e900f07a@mail.gmail.com \
--to=johnflux@gmail.com \
--cc=git@vger.kernel.org \
--cc=rdv@roalddevries.nl \
/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).