Worst part of being a fresher is to unsuccessfully trying to get the team move to git version control..

The thing to bear in mind is that the move is not free. I want our team to move from svn to git but it's a 4 year old code base with 15k commits and some questionable repo structure. It's not just a drag and drop.

And welcome to devRant!

What kind of version control are they using?

Welcome to devrant! :)

@gitcommit none

@alwaysmpe doesn't git-svn solve most of that? I've worked with got on (nearly 20 years old) svn repositories before without an issue - shouldn't you just be able to push the resulting git repo to remote and be done with it?

Just getting curious...

@theCalcaholic we've looked at doing just that, unfortunately there have been some bad moves in terms of structure and branching.

For git-svn to be able to resolve that a folder is a branch from another folder and not a new folder containing stuff merge info needs to be correctly preserved. For whatever reason there was a policy when I started to remove it (that's gone at least, but the damage is done). This results in a 20gb repo ballooning to 200gb.

Also when the repository was first created they didn't have a "trunk" directory, everything got put in root then later it was moved. So we'd either need to do some manual editing of the early commits or lose some history.

It's been a while since I looked but that's the gist of the problems.

@alwaysmpe ouch, that sounds bad. :(

@devaditya wow, that's really impressive. In a negative way of course. How have they survived till now?

They use Filezilla