From: Sitaram Chamarty <sitaramc@gmail.com>
To: Roald de Vries <rdv@roalddevries.nl>
Cc: git@vger.kernel.org
Subject: Re: backups with git
Date: Mon, 10 Aug 2009 19:08:49 +0530 [thread overview]
Message-ID: <2e24e5b90908100638m797ccf8ei8437714952b4f2d5@mail.gmail.com> (raw)
In-Reply-To: <41CB836B-6057-448E-805F-F25EAF765D27@roalddevries.nl>
On Mon, Aug 10, 2009 at 1:57 PM, Roald de Vries<rdv@roalddevries.nl> wrote:
> 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?
The two questions you have to ask yourself are: will I ever branch and
merge in this "repo", and do I really want versions from weeks and
months ago?
A "no" to the first question means you're essentially using a very
powerful VCS as a mere backup system. I suggest rdiff-backup or (if
it's mature enough now, not sure) duplicity..
A "no" to the second question means you're needlessly keeping lots of
old data, and have to jump through hoops to get rid of it if you need
to.
There's a limit to how much you can Macgyver git into doing what it is
not intended for :-)
Having said all that, I do use git to manage parts of my $HOME that do
satisfy those constraints (config files, ~/bin, etc) -- I do sometimes
branch and merge, and I do want really old versions. I do this by
putting all of them in a repo, and symlinking them to $HOME.
Regards,
Sitaram
prev parent reply other threads:[~2009-08-10 13:44 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
2009-08-10 13:20 ` Martin Langhoff
2009-08-10 13:38 ` Sitaram Chamarty [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=2e24e5b90908100638m797ccf8ei8437714952b4f2d5@mail.gmail.com \
--to=sitaramc@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).