hgweb: nodeids should be aligned in raw changesets If they aren't it breaks hg import --exact Thanks to Jesper Noehr for noticing it. [ original upstream description ]

notify: mime-encode messages - addresses will be properly encoded - message bodies will also be encoded as we are not sending patches that are meant to be applied - update test output - adapt test-keyword to ignore the new headers [ original upstream description ]

(stable) merge with default

Do not shadow builtin format (detected by pychecker)

(stable) merge with default

keyword: move common code out of commit condition

Merge with stable

keyword: be more efficient about ctx usage [ original uptstream description ]

cmdutil: use change contexts for cset-printer and cset-templater [ original uptstream description ]

Merge with stable

patch: turn patch.diff() into a generator This should even be a little faster than passing in an fp argument. [ original upstream description ]

Merge with stable

extensions: use new wrapper functions [ original upstream description]

Merge with stable

help: better documentation intro for a few extensions [ original upstream description ]

show enabled extensions in hg help [ original upstream description ]

untest

cross them fingahs

Merge with stable

fix test output broken by a04d8cadb6af

Merge with stable

Have verbose and debug flag print the changeset rev and hash when committing. Besides updating the tests output, I had to push back at the end the test for issue1193 in test-commit, solved by cset 4386a7706828, because it was using the current date for commit and was randomizing the subsequent hash. [ original upstream description ]

Backed out changeset d557749c627a Replace this change with a better one. [ original upstream description ]

(0.9.2compat) remove new verbose commit message for backwards compatibility

(stable) merge with default

Have verbose flag print the changeset hash when committing [ original upstream message ]

(0.9.2compat) add merge, resolve to restricted This is not really backwards compatible (test only as comment) and doesn't prevent extra conflicts with older Hg versions. On the other hand it doesn't do any damage either and provides the 3-way merge ease if possible.

Avoid additional conflicts during merge/resolve Make merge and resolve trigger kwtemplater.restricted to compare data without keyword expansion. The keyword stays outside the conflict: $Keyword$ <<<<<<< local bar ======= foo >>>>>>> other and will again be expanded on commit. Demonstrate in test case.