Both existing answers suggest storing your username and password unencrypted in plain-text, which is a bit of a no-no. You should use the Keyring extension instead, as it has been specifically designed for securely saving authentication passwords. It already comes bundled with TortoiseHg, so all you have to do is activate it by writing the … Read more
With the release of Mercurial 2.2, you can use the –amend option with hg commit to update the last commit with the current working directory From the command line reference: The –amend flag can be used to amend the parent of the working directory with a new commit that contains the changes in the parent … Read more
Running brew reinstall python@2 didn’t work for my existing Python 2.7 virtual environments. Inside them there were still ERROR:root:code for hash sha1 was not found errors. I encountered this problem after I ran brew upgrade openssl. And here’s the fix: $ ls /usr/local/Cellar/openssl …which shows 1.0.2t According to the existing version, run: $ brew switch … Read more
Pushing to a network share is possible, but not recommended by the Mercurial team. See the “shared disk” part in Publishing Repositories in the Mercurial wiki: generally restricted to intranets, not generally recommended due to general issues with network filesystem reliability At my workplace, we are keeping our HG repositories on a network share (on … Read more
Install Cygwin (with python, hg, git) Install git-hg run git-hg clone …url… Or tell me what the url is for this hg repo of yours, and I can convert it for you.
SVN’s merging capabilities are decent, and the simple merging scenarios work fine – e.g. release branch and trunk, where trunk tracks the commits on the RB. More complex scenarios get complicated fast. For example lets start with a stable branch (stable) and trunk. You want to demo a new feature, and prefer to base it … Read more
There’s nothing in particular in DVCSs that makes merging easier. It’s simply cultural: a DVCS wouldn’t work at all if merging were hard, so DVCS developers invest a lot of time and effort into making merging easy. CVCS users OTOH are used to crappy merging, so there’s no incentive for the developers to make it … Read more
The new things are related to MSTest stuff. This is the one that I use: # use glob syntax syntax: glob *.obj *.pdb *.user *.aps *.pch *.vspscc *.vssscc *_i.c *_p.c *.ncb *.suo *.tlb *.tlh *.bak *.[Cc]ache *.ilk *.log *.lib *.sbr *.scc *.DotSettings [Bb]in [Dd]ebug*/** obj/ [Rr]elease*/** _ReSharper*/** NDependOut/** packages/** [Tt]humbs.db [Tt]est[Rr]esult* [Bb]uild[Ll]og.* *.[Pp]ublish.xml *.resharper *.ncrunch* … Read more
Update to the stiging branch and create a new branch off of it. Then close the old branch. In summary: hg update stiging hg branch staging hg commit -m”Changing stiging branch to staging.” hg update stiging hg commit –close-branch -m”This was a typo; use staging instead.” hg push –new-branch
Using git-hg. First, make sure there is a (non-Mercurial) git submodule under your main repository. If you don’t have other submodules yet, just create a dummy submodule for some library other than core-plot, for instance: main-repo $ git submodule add https://repo.url.com/repo.git repo Second, clone the core-plot library into some directory. main-repo $ git-hg clone https://code.google.com/p/core-plot/ … Read more