hgext3rd/__init__.py

help: describe more detail about capabilities while deciding merge tool

"hg help merge-tools" describes as below:

    (internal merge tools) will by default not handle symlinks or
    binary files.

But in some cases, Mercurial assumes that internal merge tools have
one or both of these capabilities.

"hg help merge-tools" also describes as below, for matching patterns in
merge-patterns configuration section. But this is not sufficient.

    Here, binary capabilities of the merge tool are not considered.

This patch describes more detail about capabilities while deciding
merge tool.

# name space package to host third party extensions
from __future__ import absolute_import
import pkgutil
__path__ = pkgutil.extend_path(__path__, __name__)