Re: backups with git and inotify
- From
- David Tweed <david.tweed@gmail.com>
- Date
- Dec 11, 2007, 13:24 UTC
- Message-ID
- <e1dab3980712110524k59437f15pd38f74f55d692a69@mail.gmail.com>
- In-Reply-To
- <20071211102546.GA5811@bit.office.eurotux.com>
On Dec 11, 2007 10:25 AM, Luciano Rocha <luciano@eurotux.com> wrote:
Show 7 quoted lines
> On Mon, Dec 10, 2007 at 10:57:46PM +0100, Björn Steinbrink wrote: > > On 2007.12.10 20:29:11 +0000, Luciano Rocha wrote: > FWIW, I also think that trying to keep a coherent stat with automatic > commits isn't possible. As for the temporary, unneeded files, a > exclusion pattern will suffice, and using .git directly, instead of a > (FUSE) filesystem, will allow permanent storage of those temporary > files, until explicitly removed.
As a data point, I find it easier for my work to have rules that specify the files you DO want to keep. (I actually have a set of common suffixes to ignore that's checked first but purely for efficiency: it's quicker to throw out the usual suspects like *~, *.o, *.pyc, etc, immediately rather than fail to match all the more complicated "keep this" rules every single time.) One advantage of this is that if I do something stupid like drop a 2G video file into the tracked tree it's doesn't get sucked in to the git repo.
-- cheers, dave tweed__________________________ david.tweed@gmail.com Rm 124, School of Systems Engineering, University of Reading. "we had no idea that when we added templates we were adding a Turing- complete compile-time language." -- C++ standardisation committee