tansy

What's interesting, Pavlov [says](https://sourceforge.net/p/sevenzip/support-requests/498/#20ea) that > p7zip 16.02 is not affected by CVE-2023-31102

> Any help on same is really appreciated.....Anyone ? Well, all I could advice is try to find which version incorporated the bug, then compare then with diff and try...

And what's the problem? As long as archives produced are correct then difference between versions doesn't count.

There is branch [p7zip22.00](https://github.com/p7zip-project/p7zip/tree/p7zip22.00). You can make new, *p7zip23.01* branch and they may merge it into project as https://github.com/p7zip-project/p7zip/tree/p7zip23.01. Before you request a pull change source new lines from Dos...

> could that cause issues? Yes, incompatibility of pre-v23 standalone plugins in Linux/MacOS. It had nothing to do with current p7zip here, that is v17, and very likely uses linked...

> -#ifndef _UINT64_T_DECLARED > -typedef UInt64 uint64_t; > -#define _UINT64_T_DECLARED > -#endif > > I can submit a pull request if you like. What makes you think that undefining it...

> Hmm. I have certainly not heard that Microsoft is ditching CRLF Depends what you mean by 'ditch'. They still support it but not force it and not use it...

Ok, ok, i get that. Maybe, at least .gitattributes, so if you _edited them with Visual Studio 2019 they ended up with mixed line endings_? ---- > [Also some interesting,...

It would be better if all quality options were unified (proposed in #9) and all these parameters `wvlt_thrxX` put in the table and filled accordingly to the quality parameter.

There are errors on all Clangs (here 3.8 and 5.0), not only new. Not to mention GCC, that doesn't have '-fwritable-strings' since GCC-4. ~~~ $ make -f Makefile_Linux CC=clang clang...