Brief article on benchmarks of Python repository with leading DVCSen

[Nicholas Allen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> 
> Ok - as you see, I am not familiar with IDE so much. But wouldn't
> "commit often" be a solution ?

No. It may help reduce the chance of problems but a single refactoring
session in Eclipse can significantly change file contents. Hoping that
you commit often enough is a bit silly. You should commit when you want
to commit and not in order to get around some limitation in the VCS. I
probably commit about 10 times a day but I commit when I want to - which
is usually a point where there are no compile errors. When refactoring a
lot of errors can appear until the refactoring is complete. I don't want
 to commit while I am in the middle of a refactoring that doesn't even
compile.

Explicit renaming is *absolutely* critical for me. I would not want to
use git for working on Java code with Eclipse refactoring. If git
supports explicit renaming I might then consider it again but it seems
git is designed this way and for a particular purpose (which is fine if
that fits to what you want to do but it isn't for me).

Nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmWt+AACgkQ1+i51gqqEGnrLgCdElHwnUb2DzOwB2c+X0UKOyaO
MfUAoK68seasevEWMMDfesHRoaGrmRF5
=3aoD
-----END PGP SIGNATURE-----