On Wed, 8 Feb 2017 12:17:37 +0100 Cecil Westerhof <[email protected]> wrote:
> I had a talk yesterday with a company where they are using > Subversion. The reason is that all there suppliers use Subversion. I > understood it should be quit easy to communicate from Git with > Subversion repositories. Is that true? Does anyone has any > experiences to share? Git has Subversion bridge which appears to work OK for most cases. Still, it should be understood that both systems have rather drastically different world views on certain concepts of a VC system, so it's possible to reach certain corner cases IMO. Still, you can use `git svn` personally to work on source code using Git and push to Subversion server (and get updates from there). That's basically what this bridge was invented for anyway. > Also, how can I ‘sell’ the switch from Subversion to Git? I like Git > much better as Subversion, but I am afraid that is not really useful > for persuasion. ;-) Please be cold-headed on these matters. While Git indeed appeals to mid- to highly-skilled *developers,* there are other things to consider: lower-than-middle-skilled developers which constiture the largest percent of many shops involving software development and management which has concerns largely orthogonal to ease of development. I mean people in this camp will have hard time understanding why `git add --patch` and `git log -S` are cool, and the management will be obsessed with the idea that you control who can access which *part* of a repository based on the pathnames of files kept in it. Please read [2]. It shows its age (Git now works rather well on Windows, and centralized turn-key solutions for Git do exist -- if not Windows-specific) but it captures the essense of what I'm talking about pretty well. Also consider that should you actually succeed in switching be prepared to serve as a "Git go-to guy" for that shop for an indefinite amount of time, and this means both teaching the folks and dealing with things like the scenario #2 from [3] (I've witnessed such things myself). All in all, the best strategy for pushing for something over something entrenched, as usually, appears to be _gradual_ attacks. That is, form a group of supporters, and manage one simple project in Git. If that succeeds, you'll have hard facts to present before the management and the other devs. 1. https://www.kernel.org/pub/software/scm/git/docs/git-svn.html 2. http://blog.red-bean.com/sussman/?p=79 3. https://randyfay.com/content/avoiding-git-disasters-gory-story -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
