Wykres commitów

6 Commity (c87c40a981f129b8512d8b57a14c53f6f0a2a875)

Autor SHA1 Wiadomość Data
David Ward 7ca518027b tools: Determine starting commit when generating a new ChangeLog file
This was still hard-coded to 1.0.28. Detect this automatically instead
by finding the most recent release tag.
2022-05-14 17:35:43 -04:00
David Ward 7467a9da22 tools: Use topological commit ordering when generating ChangeLog files
This means that commits from the same merge request will always appear
together in the ChangeLog, instead of appearing shuffled together with
other commits that were authored around the same time.
2022-05-14 17:35:43 -04:00
David Ward 4dbfa03ec4 tools: Fix inconsistent formatting when generating ChangeLog files
Use 12-digit short hashes (which appear in merge commits). The number
of digits required to unambiguously identify a commit increases as the
Git repository grows. The ChangeLog for the 1.0.27 release has 7-digit
short hashes, which are no longer meaningful: 9 digits are needed now.
Forcing 12 digits to display here is the solution in the Linux kernel.

Do not "decorate" the log with branch or tag names. It is understood
that each file starts at a specific release tag (e.g. 1.0.27) and ends
at the next tag (1.0.28), or at HEAD for development snapshots. Topic
branch names, or the refs "master" and "HEAD", do not need labeling.
2022-05-14 17:35:43 -04:00
Olaf Meeuwissen 8f3b84f6f4 Adjust ChangeLog trailer comment to match Makefile.am comment 2019-08-26 21:53:09 +09:00
Olaf Meeuwissen 85674f1213 doc: Update as per post-release instructions 2019-08-01 21:13:33 +09:00
Olaf Meeuwissen b596f98879 Include an up-to-date ChangeLog with every build 2019-06-30 12:45:03 +09:00