On 8/20/07, Matthieu Moy <Matthieu.Moy@xxxxxxx> wrote: > OK. AAUI, you're abusing git as a backup system. Just as a point, I think a better word is "archive system". (Backups are more for replicating current state in the event of a system failure. Clearly _if_ you're working on a well defined project, careful repository management is a good idea. (One of the key things you lose from automatic commits is the ability to reliably bisect stuff.) However, not all the work one does on a computer is so focussed and well-demarcated, so in other cases keeping a history so you can, eg, look at what you're research codebase looked like when you generated the results you pasted into a paper on July 12 2005 is a useful ability, even if that sort of "looseness" wouldn't be appropriate in "product" based development. The nice thing about git is that it's so efficient at the low levels it can be used for both "proper" SCM and archival storage. -- cheers, dave tweed__________________________ david.tweed@xxxxxxxxx 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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
