TPS
Here's an even better option, if a changelog is updated, but not transcluded, use it, e.g., https://github.com/bromite/bromite/releases. But remember to include _only_ the diff of the changelog the same way,...
After reading changelog @ https://github.com/M66B/open-source-email/releases, I find that 1 can diff between version #s simply by inserting before & after ellipses, so for my example above, https://github.com/jsummers/tweakpng/compare/1.4.5...1.4.6 works! Should make...
Maybe for those who really want lean e-mail notification, the reverse should also be available, i.e., _just_ release version info, w/o any changelogs @ all.
@der-eismann Since G👊 is _only_ about the latest release anyway, that's what make sense in context.
> [The current bottleneck is zopfli algorithm, but zopfli itself does not support multi core.](https://github.com/JayXon/Leanify/issues/13#issuecomment-70749601) @JayXon An optimized version like @MrKrzYch00's [fork](https://github.com/MrKrzYch00/zopfli) _is_ multi-threaded & would solve that for you.
https://stackoverflow.com/questions/28975700/how-to-add-pthread-library-to-c-project-in-visual-studio-community-edition _seems_ to have a solution for that, but I'm unsure if that would introduce the need for a DLL dependency, or could be done for `leanify`'s monolithic executable.…
Anyone got any benchmarks? @JayXon Any plans for official binaries for such a monumental release?
@doterax No, I use leanify solely via various [FileOptimizer](https://nikkhokkho.sourceforge.io/static.php?page=FileOptimizer) toolchains, which run 1 file @ a time, so _this_ improvement would do nothing there currently.
As an intermediate to a `--keep-all-metadata`, wouldn't it be reasonable to have a `--keep-all-`*__`known`__*`-metadata` (`-kakm`, for short, maybe), which simply _combines_ all current & future `--*keep*` switches?
@andika207 https://github.com/gavinhungry/cipherfox ?