Fossil SCM

If I am reading this correctly, the JPEG and PNG bars are the ones increasing with each commit, not so much the TIFF bar due to using uncompressed TIFF

andygoth 2020-09-28 04:03 trunk
Commit 309af345ab6ae43a62dfc2b4ee3c5917cde7b8c72b7b8e985e8821a5dbad5f89
--- www/image-format-vs-repo-size.md
+++ www/image-format-vs-repo-size.md
@@ -128,11 +128,11 @@
128128
checkins, and the repository growth rate is negligible past the
129129
first commit.⁵ We owe this economy to Fossil’s delta compression
130130
feature: it is encoding each of those single-pixel changes in a very
131131
small amount of repository space.
132132
133
-* The JPEG and TIFF bars increase by large amounts on most checkins
133
+* The JPEG and PNG bars increase by large amounts on most checkins
134134
even though each checkin *also* encodes only a *single-pixel change*.
135135
136136
* The size of the first checkin in the BMP and TIFF cases is roughly
137137
the same as that for the PNG case, because both PNG and Fossil use
138138
the zlib binary data compression algorithm. This shows that for
139139
--- www/image-format-vs-repo-size.md
+++ www/image-format-vs-repo-size.md
@@ -128,11 +128,11 @@
128 checkins, and the repository growth rate is negligible past the
129 first commit.⁵ We owe this economy to Fossil’s delta compression
130 feature: it is encoding each of those single-pixel changes in a very
131 small amount of repository space.
132
133 * The JPEG and TIFF bars increase by large amounts on most checkins
134 even though each checkin *also* encodes only a *single-pixel change*.
135
136 * The size of the first checkin in the BMP and TIFF cases is roughly
137 the same as that for the PNG case, because both PNG and Fossil use
138 the zlib binary data compression algorithm. This shows that for
139
--- www/image-format-vs-repo-size.md
+++ www/image-format-vs-repo-size.md
@@ -128,11 +128,11 @@
128 checkins, and the repository growth rate is negligible past the
129 first commit.⁵ We owe this economy to Fossil’s delta compression
130 feature: it is encoding each of those single-pixel changes in a very
131 small amount of repository space.
132
133 * The JPEG and PNG bars increase by large amounts on most checkins
134 even though each checkin *also* encodes only a *single-pixel change*.
135
136 * The size of the first checkin in the BMP and TIFF cases is roughly
137 the same as that for the PNG case, because both PNG and Fossil use
138 the zlib binary data compression algorithm. This shows that for
139

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button