-
Git
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I assume you’re referring to packfiles[1], but those are (a) very much an implementation detail (they exist only to save disk space and appear basically nowhere in the git UI), and (b) not diffs—git will pack together whatever blobs its heuristics[2] think “look similar” with no regard for whether they’re actually related to each other, as long as they seem likely to gzip well together.
[1] https://git-scm.com/book/en/v2/Git-Internals-Packfiles
[2] https://github.com/git/git/blob/master/Documentation/technic...
Literally as easy as:
https://github.com/dbohdan/classless-css
And before you say I should do that myself, again, if you want your work to be comfortable to read for the world, the bare minimum involves legibility.