remembering - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Revamp code under aux/	EuAndreh	2023-04-01	1	-108/+0
\|
*	aux/: Update	EuAndreh	2021-09-01	1	-3/+10
\|
*	aux/: Update	EuAndreh	2021-07-23	1	-5/+7
\|
*	aux/: Update, adapt Makefile accordingly	EuAndreh	2021-06-26	1	-4/+24
\|
*	Makefile, README.md: Adapt to changes in aux/	EuAndreh	2021-06-26	1	-5/+2
\|
*	aux/: Update	EuAndreh	2021-06-16	1	-1/+1
\|
*	aux/workflow/assert-*: Update	EuAndreh	2021-06-13	1	-6/+29
\|
*	Update files under aux/	EuAndreh	2021-06-07	1	-6/+17
\|
*	aux/workflow/assert-readme.sh: Assert the end of the CONTRIBUTING section	EuAndreh	2021-06-06	1	-0/+12
\|
*	README.md: Add explicit "Links" and "Releases" sections	EuAndreh	2021-06-06	1	-0/+36
	Instead of generating the "Links" and "Releases" sections on the fly and adding them to the end of the README.md before processing it with aux/workflow/README.sh, embed those sections directly and use aux/workflow/assert-readme.sh to make sure the metadata is there. Before we had: 1. generate "Links" and "Releases" on the fly inside aux/workflow/README.sh; 2. add those sections to the end of the README.md; 3. use the custom pandoc build command inside the aux/workflow/README.sh file. Now we have: 1. embed "Links" and "Releases" in the README.md directly; 2. use aux/workflow/assert-readme.sh to validate the correct metadata; 3. use the vanilla aux/workflow/commonmark.sh to generate the HTML.