Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
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. -- Jerry Feldman <gaf at blu.org> Boston Linux and Unix PGP key id:3BC1EB90 PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |