You can try using fast-export: cd ~ git clone https://github.com/frej/fast-export.git git init git_repo cd git_repo ~/fast-export/hg-fast-export.sh -r /path/to/old/mercurial_repo git checkout HEAD Also have a look at this SO question. If you’re using Mercurial version below 4.6, adrihanu got your back: As he stated in his comment: “In case you use Mercurial < 4.6 and you … Read more
You could use the Timestamp extension, if creating new “reference” timestamps will not be a problem. From its website: It does this by means of a database file .hgtimestamp, residing in the repo’s root and thus being versioned. Other than this, I don’t think it’s possible. I’ve read a little about Timestamp hook, and it … 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
There is no simple / recommended way of doing this directly to an existing repository. You can however “convert” your mercurial repo to a new mercurial repo and choose a revision from where to include the history onwards via the convert.hg.startrev option hg convert –config convert.hg.startrev=1234 <source-repository> <new-repository-name> The new repo will contain everything from … Read more
I always use a combination of .hgignore and BeforeBuild (in the .csproj file) for things like this. In one of my pet projects, I have the following setup: App.config contains my real hardcoded user id and password for testing. App.config.example is identical, but with fake data like “dummy_user” and “dummy_pw”. App.config is not part of … Read more
Here’s the cheat sheet on the commands: hg update changes your working copy parent revision and also changes the file content to match this new parent revision. This means that new commits will carry on from the revision you update to. hg revert changes the file content only and leaves the working copy parent revision … Read more
The biggest difference is how the branch names are recorded in the history. With named branches the branch name is embedded in each changeset and will thus become an immutable part of the history. With clones there will be no permanent record of where a particular changeset came from. This means that clones are great … Read more
How do you configure it to ignore files? Ignore is configured in a normal text file called .hgignore in the root of your repository. Add it just like a normal file with: hg add .hgignore There are two syntax options available for file matching, glob and regexp. glob is unix-like filename expansion and regexp is … Read more
The histedit extension is exactly what you are looking for. hg histedit -o or hg histedit –outgoing will bring up a list of the outgoing changesets. From the list you can Fold 2 or more changesets creating one single changeset Drop changesets removing them from the history Reorder changesets however you like. histedit will prompt … Read more
Here’s my standard .hgignore file for use with VS2008 that was originally modified from a Git ignore file: # Ignore file for Visual Studio 2008 # use glob syntax syntax: glob # Ignore Visual Studio 2008 files *.obj *.exe *.pdb *.user *.aps *.pch *.vspscc *_i.c *_p.c *.ncb *.suo *.tlb *.tlh *.bak *.cache *.ilk *.log *.lib … Read more