From: Bart Schaefer <schaefer@brasslantern.com>
To: Oliver Kiddle <opk@zsh.org>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] README, NEWS, BUGS updates
Date: Tue, 17 Oct 2023 09:26:37 -0700 [thread overview]
Message-ID: <CAH+w=7adFidbOUYDm6og0cZjcYKoB0rZZxmd+9-GsC6ZKX5Wwg@mail.gmail.com> (raw)
In-Reply-To: <67002-1697534800.086412@ksIO.2gdy.dNcX>
On Tue, Oct 17, 2023 at 2:26 AM Oliver Kiddle <opk@zsh.org> wrote:
>
> Bart Schaefer wrote:
> > +The `watch' parameter and `log' command have moved to an autoloaded module.
>
> That was already done before 5.9 and dana mentioned it in the NEWS file
> updates for that release.
Hm, sorry about that. I scanned ChangeLog for things mentioned since
the version.mk touch but must have picked up on some later fix to the
module. Can back that out.
> That change is perhaps best suited to the list of incompatibilities so
> perhaps that's why you missed it. I rather doubt that end users will
> follow what's going on with the release notes being split between NEWS
> and README. I prefer the format used by the git project for release
> notes.
I'd have no objection to this being revised ... would we leave old
stuff behind sort of like was done for ChangeLog-4.3 et al., or fold
in past history?
> > +Many Completion/ functions have been updated to recent versions of their
> > +corresponding commands, so the results offered may have changed.
>
> That sentence applies for every release we ever do. Has been rather
> fewer changes of that sort since 5.9 than we have in most releases.
I the impression it was rather a lot in terms of individual files
touched, but agree this could be dropped too.
prev parent reply other threads:[~2023-10-17 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 21:54 Bart Schaefer
2023-10-15 22:56 ` Mikael Magnusson
2023-10-16 6:38 ` Jun T
2023-10-16 23:01 ` Bart Schaefer
2023-10-17 7:43 ` Jun T
2023-10-17 9:26 ` Oliver Kiddle
2023-10-17 16:26 ` Bart Schaefer [this message]
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='CAH+w=7adFidbOUYDm6og0cZjcYKoB0rZZxmd+9-GsC6ZKX5Wwg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=opk@zsh.org \
--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).