Git Svn Bridge Info

 Now fully understand the problem create the git-svn bridge for MercuryDPM. It is commit 709 and 710. In these commits we changed the naming convention from trunk->Trunk alpha->Alpha etc.

Now git svn clone can not follow the moving of existing branch. It simple was not designed to do this.

Conclusion:

• Only git the trunk,
• Alpha/Release/.. will be accessible only via svn,
• Trunk commits only via git, via push-requests (to be confirmed by Irana, Anthony or Thomas)
• Branches on central server

Have played with a lot options. I (Anthony Thornton) personally think the best long term solution is to run bit bucket server with SVN Mirror for Stash Bitbucket add-on. This current cannot be done in the bit bucket cloud so we would have to set it up on our own servers.

Linus Torvalds is an interesting guy. The advance git-svn options are hided you cannot even access them with one million flags. You have to manual edit a text file. On this note the file: ./git/config store some interesting information under  svn-remote tag.

DO NOT run the command below. This is a temp note for Anthony Thornton

git svn clone https://svn.mercurydpm.org/SourceCode/ -r 711 -T trunk -b Branches  -b Alpha -b Beta -t Release  --no-follow-parent -log-window-size=1000000 --ignore-path='Obsolete' <YourLocalName>

Merging procedure

1. Spin up amazon server

2. git svn fetch

3. git pull

4. git merge origin/trunk

5. git push -u Bitbucket

6. (optional - send code back) git dcommit