Re: concerns about git
- From
- David Tweed <david.tweed@gmail.com>
- Date
- Oct 13, 2008, 18:40 UTC
- Message-ID
- <e1dab3980810131140p45c62e5cs690ac190eeacc38e@mail.gmail.com>
- In-Reply-To
- <20081013181941.GT4856@spearce.org>
On Mon, Oct 13, 2008 at 7:19 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
Show 8 quoted lines
> # then every once in a while, or from a cron job > $ git push --all backup > > Of course since Git is distributed you can you use this same approach > to make backups to other systems. You can even edit the .git/config > to give the [remote "backup"] section more than one url line, so > that "git push --all backup" will send updated copies to multiple > locations at once.
Another advantage of 'git push'ing to another repository (possibly via cron) as backup is that (for technical reasons) git push has to 'parse' the new changes to your repository in order to push, so it is likely to spot corruption (eg, dying disk) at that time and when you can decide what to do about it. (I have enough backups all over the place that I don't worry about not having a 'copy' of any stuff I care about, but that there'll be some fatal corruption I don't notice immediately that then gets propagated everywhere rendering them useless.)
-- cheers, dave tweed__________________________ david.tweed@gmail.com Rm 124, School of Systems Engineering, University of Reading. "while having code so boring anyone can maintain it, use Python." -- attempted insult seen on slashdot