ChangeLog generation (was: Re: _git commit object name completion)

[Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>]

Daniel Hahler wrote on Mon, Jun 08, 2015 at 00:38:13 +0200:
> I've created a Vim function to automate the ChangeLog addition:

So at least you, me, Bart, Frank, and Mikael each has his own
implementation...

diff --git a/Etc/zsh-development-guide b/Etc/zsh-development-guide
index 7f5266b..d92b724 100644
--- a/Etc/zsh-development-guide
+++ b/Etc/zsh-development-guide
@@ -70,6 +70,19 @@ avoided further changes to our workflow.
    a commit to the master repository. Don't create a separate change for
    this: amend the existing commit in your local repository.
 
+   Several developers use scripts to automate part or all of the ChangeLog
+   workflow:
+
+     Subject: helper script for making ChangeLog entries
+     X-Seq: 33835, 33872, 34912
+     http://www.zsh.org/mla/workers/2014/msg01622.html
+     http://www.zsh.org/mla/workers/2014/msg01659.html
+     http://www.zsh.org/mla/workers/2015/msg00836.html
+
+     Subject: Re: _git commit object name completion
+     X-Seq: 35414
+     http://www.zsh.org/mla/workers/2015/msg01338.html
+
  * Do not merge your private feature branches onto the master branch: a
    linear history without merge commits is simpler to follow (and to
    bisect).

I didn't link to Bart's post in that thread as it doesn't have code in it.

The aforelinked 34912 is broken in the archives in two ways: the
assignment to AUTHOR_NAME on line 3 needs to be double quoted, and the
zsh.org archives don't show the attachments' filenames (or even delimit
the attachments).

I suppose I could throw it on my github account and reference that, but
perhaps those scripts belong somewhere in the zsh repository itself?
(e.g., in Etc/ or a new dir devscripts/ or something).  They don't
really have any use anywhere else, no other project that I know of
embeds ezmlm X-Seq numbers in commit messages.