This extension has been replaced by the built-in resolve command in 1.2 and later (before 1.2, this extension was distributed with Mercurial).
Author: Brendan Cully
0.9.4 backport: http://hg.kublai.com/mercurial/crew/raw-file/tip/hgext/imerge.py
imerge lets you split a Merge into pieces. When you start a merge with imerge, the names of all files with conflicts are recorded. You can then merge any of these files, and if the merge is successful, they will be marked as resolved. When all files are resolved, the merge is complete and you may commit it.
You can save the work you've done on the merge with hg imerge save file, which stores the revisions you are merging, the list of files with conflicts, and copies of the files you've resolved so far into file. You can later resume the merge from this point with hg imerge load file.
If no merge is in progress, hg imerge [rev] will merge the working directory with rev (defaulting to the other head if the repository only has two heads).
If a merge is in progress, hg imerge will default to merging the next unresolved file.
The following subcommands are available:
- show the current state of the merge
- show the next unresolved file merge
- merge [<file>]
merge <file>. If the file merge is successful, the file will be recorded as resolved. If no file is given, the next unresolved file will be merged.
- resolve <file>...
- mark files as successfully merged
- unresolve <file>...
- mark files as requiring merging
- save <file>
- save the state of the merge to a file to be resumed elsewhere
- load <file>
- load the state of the merge from a file created by save
Configure your .hgrc to enable the extension by adding following lines:
Related post-1.0 changes to core Mercurial
"chgset 368a4ec603cc breaks imerge", thread on Mercurial mailing list, 2008-04-14 (see http://selenic.com/repo/index.cgi/hg/rev/368a4ec603cc)
"resolve: new command": http://selenic.com/repo/index.cgi/hg/rev/92ccccb55ba3