From: Daniel Shahaf <firstname.lastname@example.org> To: Axel Beckert <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Posted zsh 5.9 Date: Sat, 14 May 2022 23:21:26 +0000 [thread overview] Message-ID: <20220514232126.GA13240@tarpaulin.shahaf.local2> (raw) In-Reply-To: <email@example.com> Axel Beckert wrote on Sun, May 15, 2022 at 00:11:31 +0200: > Hi, > > On Sat, May 14, 2022 at 03:59:35PM -0500, dana wrote: > > I've just finished posting zsh 5.9. It should be available in the usual > > places: > […] > > creating-a-release instructs us to wait a day before posting to -announce, > > which has always been followed a little loosely i think, at least by me... > > but i'll do that this time, unless someone wants me to go ahead now. > > I'll upload it to Debian unstable anyway, I as I assume there won't be > any changes anymore until tomorrow. :-) I'd rather you didn't. Backwards compatibility promises don't kick in until a release is announced, even if it has been tagged. If we pull the tarball for any reason, your users will get to keep both pieces. Cf. https://dist.apache.org/repos/dist/dev/subversion/README.html. Daniel > Debian's package checker Lintian found two typos in the documentation. > Not sure why I haven't noticed them with the release candiates. There > was no lintian update since then. > > Anyway, I propose the following patch to fix these typos and would > push it in git if there are no objections: > > diff --git a/Doc/Zsh/builtins.yo b/Doc/Zsh/builtins.yo > index 280f1d72a..641e46cf9 100644 > --- a/Doc/Zsh/builtins.yo > +++ b/Doc/Zsh/builtins.yo > @@ -1936,7 +1936,7 @@ retain their special attributes when made local. > > For each var(name)tt(=)var(value) assignment, the parameter > var(name) is set to var(value). If the assignment is omitted and var(name) > -does em(not) refer to an existing parameter, a new parameter is intialized > +does em(not) refer to an existing parameter, a new parameter is initialized > to empty string, zero, or empty array (as appropriate), em(unless) the > shell option tt(TYPESET_TO_UNSET) is set. When that option is set, > the parameter attributes are recorded but the parameter remains unset. > diff --git a/Doc/Zsh/options.yo b/Doc/Zsh/options.yo > index 443676b78..5e673eb5c 100644 > --- a/Doc/Zsh/options.yo > +++ b/Doc/Zsh/options.yo > @@ -1952,7 +1952,7 @@ pindex(NOTYPESETTOUNSET) > item(tt(TYPESET_TO_UNSET) <K> <S>)( > When declaring a new parameter with any of the `tt(typeset)' family of > related commands, the parameter remains unset unless and until a > -value is explicity assigned to it, either in the `tt(typeset)' command > +value is explicitly assigned to it, either in the `tt(typeset)' command > itself or as a later assignment statement. > ) > pindex(VERBOSE) > > Kind regards, Axel > -- > PGP: 2FF9CD59612616B5 /~\ Plain Text Ribbon Campaign, http://arc.pasp.de/ > Mail: firstname.lastname@example.org \ / Say No to HTML in E-Mail and Usenet > Mail+Jabber: email@example.com X > https://axel.beckert.ch/ / \ I love long mails: https://email.is-not-s.ms/
next prev parent reply other threads:[~2022-05-14 23:21 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-14 20:59 dana 2022-05-14 21:50 ` Daniel Shahaf 2022-05-14 21:58 ` Daniel Shahaf 2022-05-14 22:27 ` dana 2022-05-14 23:26 ` Daniel Shahaf 2022-05-14 23:28 ` Daniel Shahaf 2022-05-14 23:50 ` dana 2022-05-15 10:36 ` Daniel Shahaf 2022-05-15 21:43 ` dana 2022-05-16 23:57 ` Phil Pennock 2022-05-21 1:31 ` Daniel Shahaf 2022-05-14 22:11 ` Axel Beckert 2022-05-14 22:31 ` dana 2022-05-15 4:33 ` Bart Schaefer 2022-05-15 6:00 ` dana 2022-05-14 23:21 ` Daniel Shahaf [this message] 2022-05-14 23:35 ` Axel Beckert 2022-05-14 23:49 ` 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=20220514232126.GA13240@tarpaulin.shahaf.local2 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Posted zsh 5.9' \ /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).