I’m working to migrate a subversion <-> git mirror out of self-hosted Atlassian Bitbucket (where we use the subgit plugin) and onto a standalone subgit installation. For the git repo, we’ll be migrating from Bitbucket to Phabricator; since Phabricator is similar to Github and has a commit database on top of the git repo itself, we’ll be following the Github setup guide:
Anyway, I have two questions:
(1) The initial subversion -> git import takes a very long time, owing to the size of the repo. In the past when the mirror has broken and svn/git histories diverged, within Bitbucket we’ve had to reimport the git repo from svn, which freezes the git repo for a long time. On the current standalone version (3.3.10), if both svn and git commits continue while mirror operations are down for an extended period, is subgit sophisticated enough to Do The Right Thing™ and re-merge commit histories seamlessly, or does this require a fresh reimport from one of the sources, and we’d lose deltas committed in the interim to the other?
(2) As we’re already a paying customer and will continue to be a paying customer (simply switching from the Atlassian Bitbucket plugin to the standalone daemon), I was wondering if it might be possible to request an extension to the 7-day trial. We haven’t hit the 7-day limit, yet, but I wanted to inquire in advance of that eventuality as we continue to test the migration path.
Thanks so much!
Hudson River Trading, NYC