zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Mailing-list zsh-workers <zsh-workers@zsh.org>
Subject: Re: ChangeLogs (Re: GH:zsh-users/zsh-completions.)
Date: Thu, 02 Nov 2017 21:09:05 +0100	[thread overview]
Message-ID: <18478.1509653345@thecus.kiddle.eu> (raw)
In-Reply-To: <CAH+w=7YyxuH=gNPw6+Fz+fjsTgrFGNm7Av1=OKKRmakOJiOA-A@mail.gmail.com>

Bart wrote:
> It would actually be OK with me to stop maintaining a monolithic
> ChangeLog.  It would be more useful to generate a "release notes" file
> that has only the changes since the last such file.  That would allow
> manual corrections to said file to be preserved without concern that
> they'd be stepped on by the next auto-generate, and make it a lot
> easier to see what differs from the previous release (right now one
> has to sort of search through ChangeLog for references to the release
> event).

With auto-generating ChangeLog entries, I'd expect that you'd pass the
tag of the last release to the script. So no old ChangeLog entries would
ever be stepped on by a later auto-generation. That is irrespective of
whether the output is appended to an existing file or a new file is
created for each release. I forget exactly how Frank's script worked.

> (OTOH it means more files to search for a particular change, if you
> don't have access to the git logs.)

I don't see that as much of a problem. I nearly always do have access to
the git logs. And for old history, Changelog is already separated even
if that was originally done because CVS started to get slow once the
file got big. And I can see that for someone who does want to browse the
ChangeLog, getting just the new entries is useful: much as I often
follow an update with git log @\{1\}..

> However, *IF* we're going to continue to maintain ChangeLog, I'd
> prefer that we continue maintaining it in its present form.

I don't see any reason to change the basic form.

Oliver


  reply	other threads:[~2017-11-02 20:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7240.1507973844@thecus.kiddle.eu>
2017-10-14 14:44 ` GH:zsh-users/zsh-completions Julien Nicoulaud
2017-10-14 16:49   ` GH:zsh-users/zsh-completions Eric Cook
2017-10-16 14:29   ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-16 15:11     ` GH:zsh-users/zsh-completions Peter Stephenson
2017-10-16 15:24       ` GH:zsh-users/zsh-completions Bart Schaefer
2017-10-16 15:42         ` GH:zsh-users/zsh-completions Peter Stephenson
2017-10-16 17:49           ` GH:zsh-users/zsh-completions gi1242+zsh
2017-10-17 21:09             ` GH:zsh-users/zsh-completions Joey Pabalinas
2017-10-18 16:23               ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-19  1:09                 ` GH:zsh-users/zsh-completions Bart Schaefer
2017-10-19  4:03                   ` GH:zsh-users/zsh-completions Aaron Schrab
2017-10-19  5:24                     ` GH:zsh-users/zsh-completions Bart Schaefer
2017-11-01 23:33                   ` ChangeLogs (Re: GH:zsh-users/zsh-completions.) Oliver Kiddle
2017-11-01 23:46                     ` Bart Schaefer
2017-11-02 20:09                       ` Oliver Kiddle [this message]
2017-10-19  1:31                 ` GH:zsh-users/zsh-completions Joey Pabalinas
2017-10-19 14:37                 ` GH:zsh-users/zsh-completions Daniel Shahaf
2017-10-30 23:38                   ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-11-01 16:35                     ` GH:zsh-users/zsh-completions Daniel Shahaf
2017-11-01 22:58                       ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-16 23:00           ` GH:zsh-users/zsh-completions Bart Schaefer
2017-10-16 20:04       ` GH:zsh-users/zsh-completions Daniel Shahaf
2017-10-17  7:53       ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-17  8:41         ` GH:zsh-users/zsh-completions Peter Stephenson
2017-10-16 15:26     ` GH:zsh-users/zsh-completions gi1242+zsh
2017-10-17  9:35       ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-19 18:25         ` GH:zsh-users/zsh-completions Daniel Tameling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18478.1509653345@thecus.kiddle.eu \
    --to=okiddle@yahoo.co.uk \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).