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.

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.

Collect filename patterns, wrap dispatch._parse in uisetup Store [keyword] config in kwtools. hgcmd defaults to empty string.

Merge with stable

Adapt to new webcommands with "clean" monkey patches

(0.9.2compat) fix and simplify webcommands monkey

(0.9.2compat) add test for web changeset web filediff has no backwards compatible url, so omit. Also remove clone updating status from new hg versions.

(0.9.2compat) fix webcommand monkey patches, and adapt to most recent changes

(0.9.2compat) no conditional for web file match disabling

hgweb: refactor hgweb code [ original upstream description ]

Merge with stable

tests: add tests for hgweb to test-keyword [ original upstream description ]

Merge with stable

clone: print "updating working directory" status message With this change, "hg clone" looks like this: % hg clone http://example.com/repo/big big requesting all changes adding changesets adding manifests adding file changes added XXX changesets with XXX changes to XXX files updating working directory XXX files updated, XXX files merged, XXX files removed, XXX files unresolved So the user sees % hg clone http://example.com/repo/big big requesting all changes adding changesets adding manifests adding file changes added XXX changesets with XXX changes to XXX files updating working directory while Mercurial is writing to disk to populate the working directory With this change, "hg clone" looks like this: % hg clone big big-work updating working directory XXX files updated, XXX files merged, XXX files removed, XXX files unresolved [ original upstream description ]

tests: remove some unnecessary sleeps [ original upstream description ]

Ignore .DS_Store

(0.9.2compat) ignore .DS_Store

Merge with stable

(0.9.2compat) expand * import

Expand import * to allow Pyflakes to find problems [ original upstream description ]

(0.9.2compat) get fix from stable branch

keyword: remove "identify" and "remove" from nokwcommands These two commands care about the list of modified files returned by repo.status and we may need to do a full content comparison to populate that list. [ original upstream description ]

Merge stable with default

(0.9.2compat) incorporate changes from default branch

Rename kwx to kwtools

Fix getnode doc, add doc for patch.diff monkey

(0.9.2compat) FIX typo in hgweb monkeys

Remove whitespace at eol

(0.9.2compat) remove whitespace at eol

(0.9.2compat) get changes from default branch Note: test not yet updated, as <0.9.4 complains about symlink patch, works "in principle" though.

Do not inspect node1 for diff if node2 is given

Add test for patch.diff monkey

Make main class and hg command accessible Switch from global vars to top level dictionary. Goal: make it easier for external tools (like tortoisehg) to hook into keyword extension.

Move expand/shrink decisions into kwtemplater - do not clobber wrapper code - get rid of clumsy kwtemplater attributes

Remove obsolete variable declaration

Merge with stable

Monkeypatch patch.diff for non-interactive diffs Avoid clobbering diffs with expanded keywords eg. for notify extension.

(stable) merge with default branch

(0.9.2compat) add glog to nokwcommands

Add glog to nokwcommands

(0.9.2compat) use different names for web methods Makes it clearer that these are not redefinitions of the same methods.

(0.9.2compat) web as in default where possible

Switch off expansion for web diffs

(0.9.2compat) incorporate changes from default branch _iskwfile used by 2 functions again.

Make restrict entirely a kwtemplater attribute

keyword: declare globals in a more compact way

keyword: avoid os import by using util.splitpath

Merge with stable

test-keyword: make it run under Windows - don't cat symlink, content differs - rewrite OS specific messages - generate symlink with a bundle [ original upstream message ]

keyword: fix symlink detection under Windows [ original upstream description ]

keyword: fix mq repository detection under Windows [ original upstream description ]

(stable) merge with default branch

(0.9.2compat) make patchfile monkey work with 0.9.5

(0.9.2compat) incorporate changes from default branch Testing reveals no name conflict with RuleDispatch's dispatch module. At least not with 0.9.* release versions.

Ignore everything starting with .hg Tough luck for those who want keywords in .hgignore ;)

Monkeypatch dispatch._parse to avoid running it twice Inspired by Thomas Arendsen Hain.

Do not set up kwrepo when pulling from bundlerepo Spotted and test case provided by pmezard.

Fix pychecker warning about shadowed variable Also no underscore prefix for restrict inside reposetup.

Safeguard anything under .hg, and the .hg_archival.txt file

Prevent expansion in queue repo and for email Saveguard needed for global [keyword] filename patterns.

(0.9.2compat) discard wread/wwrite approach

(0.9.2compat) get changes from stable branch

Discard wread/wwrite approach, merge with stable A basic "hg update" did not give correct results.

Fix filewise expansion for hgweb Also make changectx argument to kwtemplater.expand.

Test unbundle null revision containing empty symlink Spotted by pmezard.

keyword: fix my string pasting thinko Spotted by Maxim Dounin [ original upstream description ]

Make nokwcommands, restricted string variables at top level - prettier syntax conforming eg. to commands.norepo - possibly easier to hook from outside

Split line continuation in 2 steps (style)

Add empty_ok argument to kwrepo.commit

Allow keyword expansion on clone If [keyword] filename patterns are specified in a global hgrc keywords will be expanded in clone. This behaviour is more consistent but also more dangerous. Specifying global, and thus more complicted, [keyword] patterns might slow things down as well. Mention this in help?

(0.9.2compat) expand keywords in raw web output, and other changes from default branch Comment out import related tests, as not always available.

Remove obsolete test message

Fix web output: expand to requested rev; kwcat: wrap cat, avoid filelog subclass

Expand keywords in hgweb rawfile output

(0.9.2compat) use templatefilters module if available; bail out in mq dir Revert to always using full definition of repo._link.

Disable expansion in mq directory; add test for qcommit There might still be problems with qsave copied patch queues.

Adapt to templatefilters module splitoff

templates: move filters to their own module This eliminates just about all Mercurial dependencies in templater.py [ original upstream description ]

Ensure that absolutized paths from hgrc do not contain ../ segments. [ original upstream description ]

stable branch: reflects latest Mercurial upstream state

(0.9.2compat) clean import handling when patchfile class available Change help and test output accordingly.

(0.9.2compat) restructure based on wwread/wwrite methods as in default branch

Handle LookupError eg. for hg convert

Add empty_ok argument to commit

Update test using kwcat

Implement kwcat command

Make kwtemplater kwrepo attribute instead of global variable

Refactor overriding wread, wwrite, wwritedata repo methods - restrict consistently to reading/writing in working dir - no cludgy sys.argv parsing anymore Eases collaboration with other extensions, or external tools like TortoiseHg. Changes in behaviour: - hg cat does not expand; will be implemented with new kwcat command - no expansion in web /display/, only in downloaded archives Thanks to Jesse Glick for inciting this approach.

(0.9.2compat) fix external hook as in default branch

Return silently when external command triggers error - make hook accept hg command as string or as function object. - intercept dispatch.ParseError as well. Kudos to Steve Borho (TortoiseHg) for testing and debugging.

(0.9.2compat) implement external call handle and hook

Implement handle and hook for external callers Allows external callers that do not use the command line to pass current hg command to keyword extension. This implementation might change in the future, if wrapping of patch.diff is possible to the effect of avoiding external handles.

Get changes from default branch; update test output

Detect restricted commands thru variable

Improve use of dictionaries - iteritems() where we do iter over dicts' items - store commithooks in dictionary (safe, as hook.hook() sorts before execution)

bugfix: avoid expansion with qfold