This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
A ChangeLog alternative?
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: libc-alpha at sourceware dot org
- Date: Thu, 31 Jan 2019 23:38:17 +0100
- Subject: A ChangeLog alternative?
Look at this:
$ git log -p -M -M -C glibc-2.28..glibc-2.29 | xz -9 | wc -c
1454172
And compare it with:
$ ls -l glibc-2.29.tar.xz
-rw-r--r-- 1 fw fw 16515488 Jan 31 19:08 glibc-2.29.tar.xz
So the additional overhead for the mirrors is quite small.
For some reason, a .tar.xz file with individual patches from “git
format-patch” is even smaller:
-rw-r--r-- 1 fw fw 1542028 Jan 31 23:35 patches.tar.xz
I wonder if this would fit the requirement to document development
history without a version control system.
Could this do away with the need for ChangeLog files completely,
whether auto-generated or not?