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.

(stable) merge with default

(0.9.2compat) fix test compatibility Comment out non-backwards compatible hgweb test (at default position). Make kwexpand nonexistent work on Windows (originally by pmezard).

Thorough hgweb testing - test hgweb while keyword extension is _enabled_ - check expansion with hgweb.file - besides log and diff, also check annotate for not expanding

(stable) merge with default

(0.9.2compat) add verify to nokwcommands

Add verify to nokwcommands after refactor in e79a8f36c2a5 Add test as well. Thanks to Guy Brand for spotting this.

(0.9.2compat) context, status refactor keeping backwards compatible fallback

(0.9.2compat) ddb8a222249b is backwards compatible

Merge with stable

util: add sort helper [ original upstream description]

status: clean up all users for unknown files [ original upstream description]

repo.status: eliminate list_ [ original upstream description]

add __len__ and __iter__ methods to repo and revlog [ original upstream description]

manifest: remove execf/linkf methods [ original upstream description]

use repo[changeid] to get a changectx [ original upstream description]

simplify flag handling add _checklink var to dirstate introduce dirstate.flagfunc switch users of util.execfunc/linkfunc to flagfunc change manifestdict.set to take a flags string change ctx.fileflags to ctx.flags change gitmode func to a dict remove util.execfunc/linkfunc [ original upstream description]

use repo.changectx(None) to get a workingctx [ original upstream description]

context: avoid using None for working parent [ original upstream description ]

use repo.changectx rather than context.changectx [ original upstream description ]

(stable) mimic cmdutil.bail_if_changed even more At the check before overwriting with kwexpand, kwshrink: - abort when in middle of merge - give terser abort message

(0.9.2compat) secure keyword arguments in backwards compatible wrappers Explicitly assign _all_ keyword args when TypeErrors must be detected.

keyword: disable expansion for annotate Keyword expansion should not be annotated. Annotate revision when unexpanded keyword was inserted. Add test.

(0.9.2compat) disable expansion for annotate

keyword: disable expansion for annotate Keyword expansion should not be annotated. Annotate revision when unexpanded keyword was inserted. Add test.

Merge after backout Revert to dispatch._parse for grabbing current command name.

Backed out changeset 10ebb9f44b99 Tests with "hg annotate" reveal that dispatch._runcommand is unreliable for our purpose.

(0.9.2compat) get some changes from default branch We stay with old-fashioned command _parsing because a _*runcommand method was introduced after 0.9.2

keyword: mimic cmdutil.bail_if_changed even more At the check before overwriting with kwexpand, kwshrink: - abort when in middle of merge - give terser abort message

keyword: use dirstate.parents to obtain current first parent This should be quicker than changectx().node()

keyword: monkeypatch dispatch._runcommand instead of _parse We want the current command, and hooking into this method makes it more transparent what we are doing.

(stable) merge with default to fix import from crew 1 hunk that removed "files" argument from patch.diff forgotten by me.

Incorporate latest changes in backwards compatible way

Fix arguments for patch.diff monkey

Merge with stable

(stable) ignore .DS_Store

match: remove files arg from repo.status and friends [ original upstream message ]

match: remove files argument from patch.diff [ original message from upstream ]

walk: remove remaining users of cmdutils.matchpats [ original message from upstream ]

Merge with stable

(stable) patches from default in 4b2c266bf059 Revert to util.binary, as checks entire data for \0 now.

(0.9.2compat) backwards compatible changes from default uisetup was introduced after 0.9.3, so not used. Therefore different handling of monkeypatches.

Reduce opt=arg syntax even more

Check for '\0' in entire data before acting util.binary might not be safe enough, as it fails eg. on certain pdf files (issue1066). In some cases this might even be a speed gain as there will be no vain re.sub(n)/search on huge data.

Make overwrite() arguments mandatory

Compact argument passing to wrapped methods

Privatize remaining monkeypatches by moving them into reposetup Make it more transparent if and when monkeypatches are needed.