I for one will have to rework 14 patches that I have to carry on our local
libtiff in Google.  From my point of view, it would be a huge benefit
having the whole codebase reformatted for consistency.  I see the current
inconsistency in every commit to libtiff as I review all of the diffs for
the library side of the code.

-kurt

On Tue, Dec 6, 2022 at 11:41 AM Bob Friesenhahn <
[email protected]> wrote:

> On Tue, 6 Dec 2022, Even Rouault wrote:
> >
> > Hoping for no strong opposition and religious discussions about code
> > formatting preferences, I'll merge this soon.
>
> I expect that there will be much anger from those hoping to produce
> useful patches for older libtiff directly from libtiff source code.
>
> There will be initial pain but patches produced from that point
> forward should be much cleaner.
>
> Bob
> --
> Bob Friesenhahn
> [email protected], http://www.simplesystems.org/users/bfriesen/
> GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
> Public Key,     http://www.simplesystems.org/users/bfriesen/public-key.txt
> _______________________________________________
> Tiff mailing list
> [email protected]
> https://lists.osgeo.org/mailman/listinfo/tiff
>
_______________________________________________
Tiff mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/tiff

Reply via email to