Geek Answers Handbook

Migrating from SVN to ...?

I am currently working on a team where we "use" the demolition repository. I say "use" because in fact everyone simply edits files directly on the server through the samba shared resources, while each time the architect commits from this server with our changes, which are then pushed to the servers.

Thus, basically, we miss the opportunity to have meaningful commit messages from different users and the ability to commit as often as we like.

I tried to interest distributed systems, and how the work process that we have can be very well configured with something like git (we do it on our local machines and then click on the change panel to review it), but I don’t feel it that I have enough experience with git. Most of my experiences with DVCS have been with mercury.

To a large extent, they work in the Windows environment using tortoisesvn and the way they are used to interacting with the system, but sometimes they use PuTTY to work on one of the Linux servers and know how to execute the command line.

How can this be done, I saw how some of the work being done to create gateways between SVNs and some DVCSs, does anyone have experience setting up and working in such an environment?

What about full-blown migrations from SVN to DVCS?

+4
source share
9 answers

If your team cannot figure out how to properly use subversion, I don't know how you can figure out their git. Moreover, they are conscious of “allowing everyone to work in the same working copy”, it will be difficult for them to grasp a distributed version control system.

In my experience, to use svn-git, you must know how to use git And you must know how to use svn. I would recommend them using svn correctly.

+20
source

Is there a reason why you don’t just want to keep your SVN repository and use it as expected that SVN is used?

Why not just check and merge everyone, use branches, etc.? Why switch if you have a repository installed?

+11
source

It seems that the problem you are describing is mainly related to the correct procedures and protocols for executing the code. getting another product will not affect people's work. you need to train them first. show them how to do something better.

In another note, I did not understand how you use tortoiceCVS to interact with SVN.

+6
source

It seems to me that choosing a version control system is not a problem. What you need to do is convince the architect that he needs to come up with some sane policies to use the version control system.

Your current svn system will be quite adequate; Let users create branches if you need to keep your luggage clean. An architect can combine them as he needs.

Now you can move to DVCS, and there are good reasons for this. But if the command is not used to use the rcs client / server, this can be a daunting task. And you could use git or hg locally, but these are workarounds for the fundamentally broken use of rcs. Get everyone to use svn first, this will be my suggestion.

Editing files for samba? Jokes aside?!

+4
source

git-svn is definitely your best bet here. You will be able to use all the functions for managing the local version and changes in the git review, but in the end you can push the “final” checks to the existing svn repository.

This has an amazing side effect allowing your team to get a little wet with git at a time (both because you can try before you buy, and because you can still use any existing deployment tools / that you developed using SVN).

There is also a nice crash course in git syntax for svn users , which you can use to increase the speed of your command.

+3
source

Your problem is not the SVN itself, but the correct use.

+3
source

As Steve Yegg said: TOOOOOLS

As others say, if you cannot force them to use svn, they will not use distributed vcs.

Do they use an IDE? If so, find IDE plugins that make svn easier. Thus, they can right-click on a file or folder in the IDE and complete the registration. If you make it easier to use a control source on a local copy, rather than directly accessing central files, you may have a chance. Then you can use TortoiseSVN for more complex tasks.

Some links to SVN plugins for popular IDEs to get you started:

And here is a list of IDE plugins from the subversion site.

+3
source

hg also works well with subversion - see https://www.mercurial-scm.org/wiki/WorkingWithSubversion . The core Python development team simply decided to switch from Subversion to Mercurial (after a long discussion and period c, where git and the bazaar were also considered); in unrelated development, the free hosting service code.google.com for open source projects adds hg support to their long-standing svn support.

+2
source

both git and bazaar have good support for svn. infact git-svn has matured quite a bit over the past few months.

try git because DVCS is really good and it is not as difficult as you make it sound.

+1
source

More articles:


All Articles