Switch to the new hg spanset API
This api was introduced in 3.2, and the indexation is not supported anymore (probably since
3.4)
Patch provided by David Douard
(see https://bitbucket.org/sjl/hg-review/pull-requests/8/better-handling-of-obsolescence-markers/diff#comment-8174971)
| author |
Christophe de Vienne <christophe@cdevienne.info> |
| date |
Fri, 19 Aug 2016 18:21:28 +0200 |
| parents |
9b78bb09a3db |
| children |
(none) |
Licensing
=========
hg-review is distributed under the same license as Mercurial itself: `GPL
version 2 or any later version
<http://bitbucket.org/sjl/hg-review/src/tip/LICENSE>`_.
If you want to create a program that works with hg-review you should look at
`Mercurial's License FAQ page <http://mercurial.selenic.com/wiki/License>`_ to
learn about how this might affect you.
The basic idea is:
* If you review code with hg-review, you are not affected by the license.
* If you bundle hg-review with another application and don't change anything,
you are not affected by the license.
* If you create an application that interacts with hg-review solely through its
command line interface or web interface, you are not affected by the license.
* If you create an application that interactes with hg-review by calling its
internal Python API, you *are* affected by the license and will need to
license your application's code as GPL version 2 or later.
Note that the last item (using hg-review's internal Python API) is probably the
one you *won't* want to do anyway, since the Python API is *not* stable.
If you have any questions please `email Steve <mailto:steve@stevelosh.com>`_,
but remember that he's not a lawyer and might not have a fast answer for tricky
questions.