Henrik Ahlgren wrote: ... > Git is an awesome tool that can be utilized with a wide variety of > files, not just software source code or text. However, it faces > scalability challenges with larger files, such as videos. While > extensions like git-annex can assist in managing these larger files, > they can struggle when dealing with tens of thousands or more of files. > > Additionally, Git's core feature of maintaining immutable history is not > well-suited for backing up large, dynamic datasets, where retaining the > entire history indefinitely may be undesirable. There may also be > privacy and legal concerns related to maintaining permanent records of > all changes, since establishing a retention policy is difficult. > > So, most people cant't have their whole $HOME in a Git repository. > > Moreover, storing Git repositories on the same storage device as your > original files only safeguards your data against your own mistakes. This > is analogous to the (opposite) misconception that RAID systems serve as > a backup solution; they only protect against hardware failures of one or > more disks, and happily mirror all your mistakes for you. Proper backup > system need to protect your data from most (ideally all) data loss > scenarios.
... unfortunately git has a fatal flaw as far as i'm concerned. it does not keep proper track of file attributes like last changed time and date and restore them properly (and yes, i know about make and issues with make not working right but to me that's not something git should have been set up wrong about to begin with, etc.). yes, there are patched ways of keeping track and restoring that information but until there is some way to have what i would consider normal archive data kept as a core feature i can't use git how i'd like. songbird
