Link Details

I never know how to decide when to try the latest, greatest tools? Maybe I'm too influenced by "if it ain't broke, don't fix it." mentality. Mercurial sounds like it has some excellent capabilities, and so does git, but our subversion system seems to do the job reliably. (knocks on wood!)

the benefit of a DVCS is you can keep all the history with you at all times. and you can do everything locally that you would do with a server present, without any problems and synch up later. great for working on a plane etc.

i just wish one distributed version control system would do auto-rename tracking properly. mercurial, bazaar and git go half way there with heuristics that use file comparisons and a threshhold to determine if a renamed file was previously something else. however, they are still prone to bad failures.

i should dig into bazaar and make it do inode tracking. inodes under unix filesystems don't change (I think that's the case with NTFS also, but not FAT) on renaming. so, you could keep track of things perfectly. and then, integration with other things which do renaming (e.g. IDEs) isn't really needed anymore. the VCS can work it out for you.