2011年11月1日 · Mercurial allows users to use and happily abuse the system without letting them make any non-recoverable mistakes. Any professional tool must come with a clearly designed and intuitive CLI. Mercurial users can do most of the work by issuing simple commands without any strange options. In Git double dash, crazy options are the norm.

It could be useful to mention that if you manually hg add ignored files Mercurial will track them. For example, if you have a bunch of files like deploy-test.conf, deploy-production.conf, etc and don't want to version them (they might have passwords in them) but you do want to version deploy-template.conf you can just ignore deploy* and manually add deploy-templace.conf.

2013年6月27日 · However, the drawback to using import/export, transplant, and cherry-picking in general is that you can't really move over G without its ancestors, because in Mercurial a changeset's name is its 'hashid' which includes the hashids of its parents. Different parents (G's new parent would be C and not F) means a different hashid, so it's not G ...

2010年12月7日 · Note3/Edit (courtesy of @JasonRCoombs): Now that phases are standard in mercurial, rebase will refuse to modify changesets that have already been pushed. Either fool it by changing the phase back to draft (with hg phases ), or let the old branch stay where it is, and just make a properly named copy (e.g., with `hg rebase --keep').

I'm using Mercurial locally for a project (it's the only repo there's no pushing/pulling to/from anywhere else). To date it's got a linear history. However, the current thing I'm working on I've now realized is a terrible approach and I want to go back to the version before I started it and implement it a different way.

2010年7月10日 · When using Mercurial, how do you undo all changes in the working directory since the last commit? It seems like this would be a simple thing, but it's escaping me. For example, let's say I have 4 commits. Then, I make some changes to my code. Then I decide that my changes are bad and I just want to go back to the state of the code at my last ...

2012年7月17日 · Update/Edit: Newer versions of mercurial may need to use. hg shelve -n "UnfinishedChanges" hg unshelve "UnfinishedChanges" You can still use --name as an alternative to -n, but mercurial doesn't seem to like --name anymore. Additionally, the --all is no longer required and mercurial will in fact freak out over it. Patch queue the items using mq ...

In TortoiseHg, right-click on the revision you want to modify. Choose Modify History->Import MQ. That will convert all the revisions up to and including the selected revision from Mercurial changesets into Mercurial Queue patches. Select the Patch you want to modify the message for, and it should automatically change the screen to the MQ editor.

2014年10月18日 · When dealing with UNPUSHED changesets I cannot see a difference between "hg strip --keep tip" and "hg backout" (tried with Mercurial 4.5.2) -- both remove the most recent changeset/commit and preserve changes –

2009年5月31日 · I am looking for an expression for the .hgignore file, to ignore all files beneath a specified folder. eg: I would like to ignore all files and folders beneath bin Actually any advice on how the