Rename "text" to "data" always as set before call to util.binary()

Reflect new scheme in function docstring

Remove all hgkwencode, kwexpander.py and updatekw.py This scheme should work just with: extension keyword.py pretxncommit-hook pretxnkw.pretxnkw

Standalone version for keyword.py Check "expand" patterns in the [keyword] config section. Removed keyword in file itself to simplify patterns. Revert (again) to basename.

Change config opt "expand" to accept filename patterns Not nice yet; but passes tests together with pretxnkw. TODO: Find out what filelog.add() does exactly.

Interim test version in connection with keyword.py Simplify grep pattern. Outcomment filename lookup, will be changed to configitems('keywords'). Update stuff will be removed. And the whole thing will go into pretxncommit. kwupdate.py will be removed.

Make keyword do my hgkeyword; use basename again add() needs only str.replace(). TODO: Make even more compatible with cvs' $Id$? (date UTC, slashes) Check config before reading. And!: Use config file patterns, in cooperation with pretxnkw. This will expand keywords alread on commit!

Add original keyword extension by Thomas Arendsen Hain

Update function descriptions

Add TODO for walk back through file history on update

Test for binary

Clean up variable names; do not explicitly return False

Do not explicitly exit False; rename node1/2 to r1/2, p1/2 to n1/2

Do not explicitly return False at end

Reparse cmdline to avoid expansion in uncommitted files

Make wwritekw() and all vars local

Throw out demandimport -- at least temporarily

Double check encode filtered filenames

Added tag universal_scheme for changeset 536c1797202d

Implement $Hg$ scheme with update hook The pivotal line for update hook is: repo.dirstate.update(kwupdates, 'n') This forces hg to consider the freshly written files as not modified. Thanks to wfile(), this keeps executable bits etc. Still needs more testing. No need to check for basename/filename in keyword trigger. update hook does not need re. TODO: Walk back in history, if last change of file didn't happen in 1 of the provided changesets (update/merge?)?

Simplify for $Hg$ expansion scheme

Use the "parent1|2" kwargs to detect file state Can parent2 be of further use? Like in parsing back history? Adapt keyword trigger to $Hg$ scheme.

Simplify filter pattern for $Hg$ scheme Adapt keyword trigger as well.

Start universal $Hg$ keyword expansion

Rename parent1 to p

Rename lr variable to repo

Adapt to filename instead of basename style

Short "f" for "filename" iteration variable

Added tag filename for changeset 56a61a5c696d

Switch to complete filename in first keyword field This will hopefully allow to iterate over the stream in hgkwdecode, and lookup the relatively latest revision of corresponding file.