One of the possible changes you might make to your codebase is to delete
or rename a file. Git will track that. In a versioning filesystem,
doesn't that cause all the versions of the file to get deleted or renamed?
Mark
On 5/4/2012 4:46 PM, Jerry Feldman wrote:
On 05/04/2012 09:18 AM, Greg Rundlett (freephile) wrote:
At the risk of oversimplifying, you might consider git a versioned
file system. And for "automatic" versioning of /etc, I have to say
etckeeper [1] is "a keeper" :-)
I use git for my work projects, and I have use many other code control
programs. But, they are NOT versioning in the sense of VMS. For instance
in git (and other code management systems) you must explicitly check in
your changes (such as git commit). With a versioning file system,
everytime you save a file a backup version is kept up to the limit set
by the system (or you). Let's say I am working on a piece of code, and I
save it, but don't check it in, then the next day, I really screw
something up in that file, but I have saved it. If I want to recover
from git (or svn, or cvs, ...) I've lost some of my changes. With a VMS
style of versioning, every time I save the file I get a new version.
_______________________________________________
Discuss mailing list
[email protected]
http://lists.blu.org/mailman/listinfo/discuss
