commitsigs & Mercurial 5.6

[Raphaël Gomès]

On 1/4/21 11:25 AM, A. Klitzing wrote:
> Hi there,
Hello André,
> the latest Mercurial 5.6 changed "files" on the changeset object and
> broke the extension commitsigs.
Could you tell us what you mean by "broke"? What happens exactly? Are 
the contents of `files` different? Do you get an error message, a traceback?
> As I don't have enough experience about that new "API" it would be
> nice if someone could help here.
> How can I get the same files from new API as provided from the old API
> to avoid breaking existing hashes?
>
> https://foss.heptapod.net/mercurial/commitsigs/-/blob/branch/default/commitsigs.py#L216

Happy new year,
Raphaël

> Best regards
>     André Klitzing
> _______________________________________________
> Mercurial mailing list
> Mercurial at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial