Bob Friesenhahn

If you are able to select the default branch, that would be fantastic.

I asked Google this question: "mercurial how to assure that files are treated as binary" and it says that mercurial stores all files as binary. It also says: The distinction between text and binary is primarily for user-facing tools (like hg diff), which try to show human-readable changes, but will show "binary files differ" if NUL bytes are present That is the message I saw. It suggests adding a "[merge-patterns]" section to .hgrc and therefore I added this to my .hgrc: [merge-patterns] **.fpx =...

Please make sure that you use a very descriptive branch name, especially since Mercurial does not allow changing history. The generic branch name you used for libtiff can only be used the one time. It would have been much better if it had included the libtiff version.

Yes, just provide proposed ChangeLog text, and I will take care of that part of the update. This is helpful since I update ChangeLog often, and many times, there will be a change of the date at the top of the ChangeLog and thus an automatic re-generation of some dependent files. It would be perhaps better if most generated files were removed from the Mercurial repository (they would still be in distribution archives) but I am not sure what the scope of the impact would be. For example, web sites...

Update libtiff

I merged your your branch into main (after fixing a Magick++ compilation bug that I had created) and closed the branch so it does not show up in the branches listing. Unlike git, Mercurial history is totally immutable. This means that the branch which was created will always be present, even though the branch has been "closed". I had to do this in order to push changes: % hg push pushing to GM searching for changes abort: push creates new remote branches: Update libtiff (1 closed) (use 'hg push --new-branch'...

In the future, please avoid updating the top-level ChangeLog given that this is assured to cause a large merge conflict. There are many generated files which depend on ChangeLog. The HTML files are generated based on ChangeLog, and the date at the top of the ChangeLog file is used as the release date for the whole package. For unknown reasons, all of the binary PerlMagick/t/fpx/input files were modified. Maybe Microsoft Windows did that. I will revert this change. I see that tiff-4.7.1/cmake/Findliblzma.cmake...

Kevin, FYI, development GraphicsMagick has advanced quite a lot when it comes to reading HEIF and even HEIF sequences. While HEIF sequences can be read, there is surely more to do in order to play them like a video. Libheif itself is still not entirely evolved when it comes to sequences. Please take a look and provide feedback.