Weekly edition	Kernel	Security	Distributions	Contact Us	Search
Archives	Calendar	Subscribe	Write for LWN	LWN.net FAQ	Sponsors

A proposed Subversion vision and roadmap

Posted Apr 3, 2010 17:31 UTC (Sat) by marcH (subscriber, #57642)
In reply to: A proposed Subversion vision and roadmap by lmb
Parent article: A proposed Subversion vision and roadmap

> The opposition comes from fear of change or misunderstandings (namely, the perception that all the DVCS features need to be used or understood in all scenarios)

I think the point you are missing is the following: some workplaces want to make sure developers cannot be creative and cannot even think of any workflow different from the official one.

(Log in to post comments)

Workflow

Posted Apr 4, 2010 7:11 UTC (Sun) by smurf (subscriber, #17840) [Link]

As long as people can email (or carry USB sticks with) files to each other, the only technical result of auch restriction-from-above is that the inofficial workflow won't be documented in the VCS.

Whhy anybody would want its mmany social ramifications, all of which detrimental, is beyond me, but then there's a reason why I'm not a manager. :-P

Workflow

Posted Apr 6, 2010 19:36 UTC (Tue) by marcH (subscriber, #57642) [Link]

So you are using a centralized VC. You require some piece code from your collegue and he is not keen on committing it yet. He sends you an early version as a patch (by email or USB or else). You work on top of that. Great, but good luck committing anything. Meanwhile your collegue updates his patch. How do you merge his new stuff since he can only give his whole work from scratch? Etc.

Soon enough you give up this strange and doomed experiment of using a centralized tool in a decentralized fashion and you create a branch for the two of you.