Hi, see comments below.
2. "Regression hunting" is far more easier Sometimes we get report that "something worked in previous version but now doesn't". When I would like to check which commit introduced regression I have to use git-svn utility and then use git-bisect. Without Git it's quite hard to find which commit caused problems.
There are actually svn-bisect tools available. See for example http://uint32t.blogspot.com/2008/07/svn-bisect.html. If I understand http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481858 correctly, a svn-bisect is also included in the (current experimental) Debian package.
3. No Internet, no development Every operation, like print of development history or print diff between specific revisions need Internet connectivity. Without access to central SVN repository development is quite hard. Additionaly I hate when I have to wait for every operation with repository. It is simply annoying.
I admit that GIT certainly has more/better support for this, but if you plan ahead, the problem above can be solved by simply rsyncing the Subversion repository before you disconnect from the net. You do this with a command such as:
rsync -av tigervnc.svn.sourceforge.net::svn/tigervnc/* .The first time it takes a minute or so, but on the next update, the sync only takes a few seconds. You can then switch your working copy over the the local repo.
4. Authorship of patches There is no possibility to keep authorship of patch in SVN. If someone send us a patch then commit author is someone of us. We can only mention in commit message that patch author is person X. With Git you can easily preserve original authorship.
I don't consider this to be a major problem. If it is, we can always store the original author in a SVN attribute.
I believe there are far more arguments for Git which I didn't mention above - in my opinion it is far more better version control system for projects than SVN.
I'm sure there are a lot of arguments for Git, but there are also arguments against it. The lack of a good Windows version is one such argument.
I'm with DRC on this one; I don't see that the problems with Subversion are big enough to motivate training/migration/adaption to Git.
Best regards, ---
Peter Åstrand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Linköping Phone: +46-13-21 46 00
------------------------------------------------------------------------------
_______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
