On 2018/04/26 18:00, Thomas Frohwein wrote: > Thanks Stuart for identifying the problem with zstd and pointing me in > in the right direction. I added a patch that reverts upstream's commit > from October 26, 2017 that introduces the long-range matching which > uses experimental/private APIs of zstd. Those APIs are not (yet?) > exposed publicly in stable releases of zstd (see github issue #17374 > that Stuart pointed out to me).
These changes are all good and I didn't have any other concerns, OK sthen@ if somebody would like to import.
