Signed-off-by: Eric S. Raymond <esr@thyrsus.com>

This fixes a corner case where if you had a non-ASCII character in a
commit and a filter command, you would end up with an unicode string and
irkerhook.py would crash.
But it would somehow work if you did not have a filter command.
For both modes cases to work, forcing unicode in do() and then using
unicode methods are required.
JSON is unicode by default, and this is why the issues happened.

Signed-off-by: Eric S. Raymond <esr@thyrsus.com>

Signed-off-by: Eric S. Raymond <esr@thyrsus.com>

Signed-off-by: Eric S. Raymond <esr@thyrsus.com>

They tend to produce unwanted effects when an mIRC code is directly
followed by a text digit (which is going to happen often in this context, e.g.
with git hex commit IDs). the mIRC codes have no end delimiter, so
unless the client's recognizer is very carefully crafted it will eat
following text.

- use the right config for Mercurial extractor
- use the default tinyifier if nothing is provided
- support using no tinyifier (=none or empty)

Signed-off-by: Eric S. Raymond <esr@thyrsus.com>

Not quite the same as laurentb's design; this one passes all the
commit and extractor data as a single JSON object, and expect to get
back same.

Considered faster according to:
http://stackoverflow.com/questions/712791/json-and-simplejson-module-differences-in-python
http://stackoverflow.com/questions/706101/python-json-decoding-performance



As a side-effect, it might make irker work under Python versions older than 2.6.

Signed-off-by: Eric S. Raymond <esr@thyrsus.com>

With manpage documentation including example script.
Also add the full e-mail to the available metadata (only git for now).

Signed-off-by: Eric S. Raymond <esr@thyrsus.com>

Signed-off-by: Eric S. Raymond <esr@thyrsus.com>