From: Bart Schaefer <email@example.com> To: dana <firstname.lastname@example.org> Cc: Zsh hackers list <email@example.com> Subject: Re: [PATCH] Change documentation, dedication, loose ends Date: Sun, 3 Apr 2022 09:34:42 -0700 [thread overview] Message-ID: <CAH+w=7Y1i68FGUh1DL6whVrJT6SYWgd8Mugfw60yck9Nq5Tz4A@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Sat, Apr 2, 2022 at 8:31 PM dana <email@example.com> wrote: > > * In workers/47922 Daniel had suggested some changes to the documentation > for the CASE_PATHS option Bart added; these changes were never merged or > commented on. Are we satisfied with Bart's original documentation? I didn't find the rewrite to be significantly clearer than what I wrote, but obviously I might be biased. > > -Changes since 5.8 > +Changes since 5.8.1 I almost did this in the NEWS patch I sent a few days ago, but then decided there wasn't much benefit to adding a 5.8.1 subsection and that I didn't want to bury the CVE mention below all the changes that (in real life but not release cycle) preceded it. > compinit: A "y" response to the "Ignore ... and continue?" prompt removes It was suggested that we change this prompt, too. Votes? > +Incompatibilities between 5.7.1 and 5.8.1 This seems wrong. The incompatibilities are either between 5.7.1 and 5.8, or between 5.8 and 5.8.1 If we're adding a sections specifically for 5.8.1, should the line-buffering bug be mentioned?
next prev parent reply other threads:[~2022-04-03 16:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-03 3:29 dana 2022-04-03 9:23 ` PATCH: _brace_parameter: add (-) Mikael Magnusson 2022-04-03 21:13 ` Mikael Magnusson 2022-04-03 16:34 ` Bart Schaefer [this message] 2022-04-03 19:18 ` [PATCH] Change documentation, dedication, loose ends dana 2022-04-03 20:59 ` Mikael Magnusson 2022-04-08 19:29 ` dana 2022-04-10 21:20 ` Daniel Shahaf
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=7Y1i68FGUh1DL6whVrJT6SYWgd8Mugfw60yck9Nq5Tz4A@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] Change documentation, dedication, loose ends' \ /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
Code repositories for project(s) associated with this 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).