Re: What's the best way to make my company migrate to Git?

[Michael J Gruber <git@drmicha.warpmail.net>]

Daniele Segato venit, vidit, dixit 01.06.2010 18:00:
> On Mon, May 31, 2010 at 10:04 PM, Andrew Sayers
> <andrew-git@pileofstuff.org> wrote:
>> On 25/05/10 08:42, Michael J Gruber wrote:
>>>
>>> Feel free to contribute to the Git Wiki maybe at
>>>
>>> https://git.wiki.kernel.org/index.php/GitDocumentation
>>>
>>> in the "User contributed Documentation" section.
>>>
>>> Michael
>>>
>>
>> Thanks for the hint - this turned into rather more than just uploading a
>> PDF, and I've now finished a complete write-up here:
>>
>>        https://git.wiki.kernel.org/index.php/SvnMigration
> 
> 
> That's a great job!
> 
> I want to point out some difficulties I encountered switching from
> Subversion to Git-SVN.
> I'd like to discuss them here before, eventually, contributing them to
> that page.

Andrew's main thrust is how to migrate a team, not how to migrate a code
base, and even less about the technical differences between svn and git.
And that makes it especially valuable.

I'd suggest not mixing these things. Andrew's page fills a gap about the
social aspects of the migration, and does so very well. He mentions very
few technical aspects, only those which you need to take into account
for planning out your team migration, i.e. relevant to advocacy, change
of philosophy, avoiding typical pitfalls.

There's already a score of pages about technical differences between git
and svn. So, please, add your technical aspects to those (or improve and
correct them), and/or link to corresponding or new pages from
SvnMigration under "See Also".

If you have additions to the migration aspects feel free to add them to
SvnMigration, of course. I know there's no sharp line but I don't want
to see a can of technical worms opened on that page :)

Cheers,
Michael