Yes, it is. Open up TortoiseHg Workbench on top of your repository. Then click the Manifest button, it looks like this in the toolbar: In the list, find the file you want to look at, right-click and choose File History: In the dialog that opens up, in the toolbar just above the file contents, click … Read more
Removing the .hg folder is sufficient. You will lose the VCS metadata (project history, previous versions of all files), which is stored there.
You no longer have to mess with the .ini file. As long as you have both TortoiseHG and WinMerge installed you will see it as an option in TortoiseHG Global Settings – TortoiseHG section – Three-way Merge Tool and Visual Diff Tool. It shows up as “winmergeu”. Banged my head against the wall for a … Read more
You want hg backout Revert/undo the effect of an earlier changeset… Backout works by applying a changeset that’s the opposite of the changeset to be backed out. That new changeset is committed to the repository, and eventually merged…
The example you give is more a Merge than really a Close. Also, if it’s that simple, you probably don’t want/need to create a named branch. But if you really want to close a branch through TortoiseHg, eg you created the NewFeature branch then both the Default branch and NewFeature branches were modified then if … Read more
Update: According to the Mercurial config documentation the defaults section is deprecated. The Mercurial wiki is also particularly critical of their use. The recommended replacement is to create a command alias (while not shadowing built in commands) that provides the functionality you are looking for. Here’s what I’ve switched to in my config. [alias] undo … Read more
No, because a tag is an entry in the .hgtags file at the root of your repository containing the changeset id and the tag name, and this file itself is under revision control. The changeset id isn’t known until the changeset is created, so tagging creates another changeset to check in the .hgtags file recording … Read more
You could probably try this stuff out and learn it more quickly than writing up your question took, but I’ll bite. Can any or all of these steps be executed with TortoiseHG, as of version 0.9.2? If yes, how? TortiseHG doesn’t yet put GUI wrappers around sub-repo creation, but TortiseHG has always done a great … Read more
Right click on the file -> TortoiseHG -> Forget Files. Click Forget. Commit and Sync. Edit: You’ll also want to add the path to your .hgignore to keep it from getting added again. You can right click on the file in the HG Commit dialog and choose to ignore it.
hg rollback reverts the last transaction, so you’d be left with unfinished merge, which you have to use hg update -C to get out. If you don’t want *b (you have it in another clone), then enable the built-in MQ extension and run hg strip -r <*b>. It will get rid of *b and *merge. … Read more