setrbuyers.blogg.se

1. MERCURIAL TORTOISEHG SEE LIST OF ALL ACTIVE PUBLIC BRANCHES MAC OSX
2. MERCURIAL TORTOISEHG SEE LIST OF ALL ACTIVE PUBLIC BRANCHES UPDATE
3. MERCURIAL TORTOISEHG SEE LIST OF ALL ACTIVE PUBLIC BRANCHES CODE
4. MERCURIAL TORTOISEHG SEE LIST OF ALL ACTIVE PUBLIC BRANCHES FREE

But it looked like it only converts the current branch, not all at once (*). I did try hg-init with TortoiseHG, and this answer gave me a good start. I did not try fast-export and hg-fast-export, since they require that you have Python and some Mercurial Python modules on your machine, which I didn't have. I had non-ASCII and (being a Windows user) non-UTF8-encoded characters (for the curious: German umlaute) in my commit messages and file names.I wanted to convert all (in my case: two, or in general: more than one) branches of my repo.I had a similar task to do, but it contained some aspects that were not sufficiently covered by the other answers here: Therefore my final thought is to keep the original anyway.Įdit: If you just want the latest commit in git, this is simpler than the above merge: hg book -r tip master I don't think that is too serious, but I may well live to regret this as an oversight. Hg push git+ssh:// :myaccount/myrepo.gitĪfter this I had a verifiably equivalent project in git, however all the orphaned branches I mentioned earlier are gone.

MERCURIAL TORTOISEHG SEE LIST OF ALL ACTIVE PUBLIC BRANCHES UPDATE

I did the following in order to get the repo ready for a second conversion attempt: hg update -C stable Without properly understanding both Mercurial and the repo to be converted, you are probably better off not doing the conversion. Moreover, I also discovered that the tip of the repo was a hotfix not yet merged with the 'stable' branch. The theory is that the default branch can be deemed to be master when pushing to git, and in my case I inherited a repo where they used 'stable' as the equivalent of master.

MERCURIAL TORTOISEHG SEE LIST OF ALL ACTIVE PUBLIC BRANCHES CODE

This is because this line of code must be viewed as a guide only: $ hg bookmark -r default master # make a bookmark of master for default, so a ref gets created Upon first pushing the project per (3) I ended up with all new changes missing.

I then had success with: hg push git+ssh:// :myaccount/myrepo.gitĪll the above are blunt instruments and I only pushed ahead because it took enough time to get the team to use git properly.

MERCURIAL TORTOISEHG SEE LIST OF ALL ACTIVE PUBLIC BRANCHES MAC OSX

FYI on Mac OSX I installed hg-git via macports as follows: The Hg-Git mercurial plugin ( ) did work for me. I raised a support ticket and will share the result if they reply.

I could choose between Git-only and Mercurial-only repos and there is no option to switch.

MERCURIAL TORTOISEHG SEE LIST OF ALL ACTIVE PUBLIC BRANCHES FREE

Kiln Harmony does not appear to exist on a free tier account as suggested above. This all seemed a bit rough around the edges, so I moved on to Kiln Harmony ( ) 2. I think that this repo had a good few orphaned branches and that hg-fast-export needs a somewhat idealised repo. Upon completion of the hg-fast-export I ended up with an amputated repo. Next I got this error:Įrror: cannot lock ref 'refs/heads/stable': 'refs/heads/stable/sub-branch-name' exists cannot create 'refs/heads/stable' Using hg-fast-export failed and I needed -force as noted above. You will now work on the new branch by default.Some notes of my experience converting Mercurial to Git. The new branch will be created and your changes committed to it. Select the “Open a new named branch” option and give it a name. Pressing it will bring up a windows with several branch options: When you are ready to commit, look for the “Branch: ****” button on the top toolbar of the commit window: To manually create a new branch, simply make changes as normal on the existing repository. Fortunately, manually creating a branch is also straightforward in TortoiseHG (if not obvious). That is easy and straightforward in TortoiseHG, but today I wanted to create a branch using my existing repository. Normally, when I wanted to work on a branch, I would clone a repository and work on the branch from that clone. I have generally been very happy and have taken frequent advantage of its ability to clone and branch cheaply. I have settled on Mercurial (through TortoiseHG) for my source control needs. Any project, no matter how small, can be improved by the use of source control.