Yes having a version tracking system set up can serve as a recovery tool in
the event of data loss, but other backup strategies have more to offer. Git
as backup is likely to demand ever growing space requirements as it lacks
pruning and rotation schedules. Also it depends on the user to actively
push everything out for backup which is all backwards. A backup system
typically pulls all the files, so If you neglect to add it to tracking,
commit and push, you put data at risk.
Other issues with using git for backup is that it does not preserve most
filesystem metadata. Specifically, git does not record:
- file groups
- file owners
- file permissions (other than "is this executable")
- extended attributes
Although their might be workarounds to that, and I suppose Git as backup is
better than no backup at all.
On Mon, Oct 8, 2012 at 8:47 AM, Charles Manning <cdhmann...@gmail.com>wrote:
> I think git is great for backup. Here's why:
> With svn etc there is a "central server". If that fails, then you are
> With git, all the clones have exactly the same data, including history
> etc. There is no "master" except by convention. If the "master server"
> dies, then just repopulate it from a "client" and you have everything
> I use git all the time even if the code does not leave one machine. It
> allows me to track changes and experiment and easily give my clients
> On Sun, Oct 7, 2012 at 5:38 PM, Max Hodges <m...@whiterabbitpress.com>
> > Git is for version tracking--most often for code, but it could also be
> > to track any files. Its not a backup tool and its not a deployment tool.
> > Tracking changes to your source code is a very useful function. Sometimes
> > during development you realize you're taken a wrong turn, and a tool like
> > Git allows you to backtrack very easily. Also sometimes you may comment
> > a lot of lines while you're refactoring some code. With Git you no longer
> > need to comment them out. Just delete them, because you can always
> > your new code with an older version. So this makes your code a bit more
> > clean.
> > I'd recommend Git any software development project. Source code version
> > tracking is as fundamental as testing. Its the professional way to
> > If you don't care about the benefits of source code tracking, and are
> > looking for a backup solution, then there are more simple ways to
> > implementing a backup, including a simply copy command to an external
> > drive or USB thumb drive.
> > As far as setting up your code for tracking, its extremely easy. You can
> > a GUI to manage things--I use the SmartGit GUI, but the command-line
> > tutorials like this one are still very useful to get familiar with the
> > concepts and capabilities:
> > http://gitimmersion.com/
> > airborne IR cameras huh? for spotting the tell-tale footprints of grow
> > marijuana production by chance?
> > Cheers!
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Git for human beings" group.
> > To post to this group, send email to firstname.lastname@example.org.
> > To unsubscribe from this group, send email to
> > git-users+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> > http://groups.google.com/group/git-users?hl=en.
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To post to this group, send email to email@example.com.
> To unsubscribe from this group, send email to
> For more options, visit this group at
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to
For more options, visit this group at