This is what branch_bookmark_suffix setting above does: only bookmarks ending with _migrate are converted. There are two caveat with this: bookmarks can not have the same name as a branch, and what if you want to use bookmarks you don’t want to push Git? Here comes the trick: mark bookmarks with a special suffix, and Hg-Git will only convert these bookmarks. To circumvent the issue with branches, Hg-Git translates Git branches to Hg bookmarks and back. Mercurial’s bookmarks are more similar to Git’s branch: they are (mutable) references to commits. That is, in Hg multiple commits belong to a single branch. In Git, they are just simple references to commits. Clone your mercurial repository somewhere, and let’s start migrating! Setting up branchesīranches in Hg and Git are slightly different. Insert the following lines in mercurial.ini: Note the format of the email after the username, Git requires exactly this structure! Now we have to just point Hg-Git to this file. This tells Hg-Git to map hg_user1 to git_user1 and hg_user2 to git_user2. We use an author.txt file: hg_user1 = git_user1
Since Mercurial only stores the author name and Git needs the email as well, we have to set up a mapping between the two.
We will get back to branch_bookmark_suffix later. You just have to specify the path to Hg-Git. It is very easy, just clone the repository somewhere and add the following lines to your mercurial.ini: By then end of our migration, a 600M repository was reduced to a 140M one! Setting up Hg-Gitįirst and foremost we have to set up Hg-Git. The migration was also the perfect time to clean up the repo and remove some large files that were accidentally committed to the repository. Obviously, for cloning we just needed pushing. Hg-Git is a nice Hg extension that lets you push and pull from remote Git repositories. In this post I summarize how the migration was done using Hg-Git. Thus, we had to migrate to Git, eventually. No wonder that Bitbucket decided to stop supporting Mercurial repositories from 2020 February. Much has changed since, Git won the DVCS war and Mercurial is losing popularity.
#Bitbucket push with tortoisehg free
Back then we simply decided based on available hosting services (Github was not big and did not have free private repos). Since our repo was relatively small, speed was never a concern. At the same time it also makes it slower. Mercurial has the advantage that it was written in Python so it is very easy to extend. We made the choice of using Hg seven years ago, when the popularity contest between Git and Hg wasn’t over yet. At Algeo we used Mercurial for version control at Bitbucket.
0 kommentar(er)
