commit: move editor outside transaction The commit editor is now invoked before files and manifest are committed. The editor is now run with only the wlock held and aborting an edit no longer requires rolling back a transaction. Changes to files during a commit still result in undefined behavior. (This is preliminary work for committing subrepositories) [ original upstream message ]

Merge with stable

commit: move commit editor to cmdutil, pass as function [ original upstream message ]

commit: drop unused p1 and p2 args [ original upstream message ]

Merge with stable

updated license to be explicit about GPL version 2 [ original upstream message ]

Merge with stable

replace util.sort with sorted built-in This is marginally faster for small and moderately-sized lists [ original upstream message ]

Merge with stable

tests: removed redundant "-d '0 0'" from test scripts The tests are executed with a .hgrc file which adds "-d '0 0'" by default. [ original upstream message ]

Merge with stable

switch lock releasing in the extensions from gc to explicit [ original upstream message ]

Merge with stable

keyword: set overwrite message only once, not for each file [ original upstream message ]

keyword, i18n: avoid untranslated strings as message parameters [ original upstream message ]

Merge with stable

expand "repo" to "repository" in help texts [ original upstream message ]

Merge with stable

keyword: word-wrap help texts at 70 characters [ original upstream description ]

Merge with stable

bundlerepo: reintroduce dirstate [ original upstream description ]

Merge with stable

add --git option to commands supporting --patch (log, incoming, history, tip) No short -g form, since it would conflict with -g from the graphlog extension. [ original upstream descrition]

patch: pass an opener to patchfile [ original upstream description ]

merge: better error messages to lead users to hg update --clean to abandon merges. Fixes issue1533. [ original upstream description ]

mq: lowercase output This extension produces quite a lot of informational messages during its normal operation and it is hard to say which strings can be changed and which cannot. [ original upstream description ]

(0.9.2compat) do not use builtin format

(stable) merge with default

keyword: simplify repo.local and bundle check (as in 2f4a399a8787)

Merge with stable

get-with-headers: fix stream modes under Windows [ original upstream descripton ]

hgweb: return meaningful HTTP status codes instead of nonsense [ original upstream description ]

Add a test for getting raw files via the web UI. [ original upstream description ]

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.