| |||||||||||||
A proposed Subversion vision and roadmapA proposed Subversion vision and roadmapPosted Apr 3, 2010 23:44 UTC (Sat) by marcH (subscriber, #57642)In reply to: A proposed Subversion vision and roadmap by cbcbcb Parent article: A proposed Subversion vision and roadmap
> 1. DVCS means there's a copy on everybody's desktop. All in the same building.
No.
> 2. developers can't make a mess of the repository metadata.
Care to elaborate? I've seen interesting screw-ups of SVN repositories. Inconsiderate developers will screw-up anything. This depends on the workflow not on the tool(s).
> 3. Svn authentication is delagated to the owners of the repository, it doesn't require sysadmins to get involved tweaking UNIX groups.
I am afraid this is your only point. I am not sure how convenient it is to emulate SVN's authentication model with the various DVCS out there.
> 4. Svn provides the means to automatically check commits on the server,
Come on, any system has hooks.
> 5. Svn works properly on windows.
Git is not the only DVCS.
> 6. Svn can represent empty directories. AFAIK git can't.
I'm really impressed. Use a hidden file?
> trying to tell svn users that the svn features they use and git/hg/bzr/etc don't have are useless is a waste of everybody's time.
It would be but I seldom hear this. What I most often hear and read and see is how DVCS offer 99% of SVN's features (and more).
> It would be great if somebody could set up the tools to support a corporate environment while also exploiting the advantages of a dvcs
Agreed.
(Log in to post comments)
A proposed Subversion vision and roadmap Posted Apr 5, 2010 15:34 UTC (Mon) by bronson (subscriber, #4806) [Link]
>> trying to tell svn users that the svn features they use and git/hg/bzr/etc don't have are useless is a waste of everybody's time.
>It would be but I seldom hear this.
You said it yourself. Check out your snide reply to #6.
|
|||||||||||||