zsh-workers
 help / color / mirror / code / Atom feed
From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] NEWS and README items about ERR_EXIT and ERR_RETURN changes
Date: Tue, 13 Dec 2022 03:20:16 +0000	[thread overview]
Message-ID: <1246e25a-9ec9-4b02-828d-c94a1a8e5ca1@app.fastmail.com> (raw)
In-Reply-To: <CAGdYchuXO2Y1Hvf0TUniL0_UwzFBv2d4jWktbABL1k_b1p_OpA@mail.gmail.com>

Philippe Altherr wrote on Mon, 12 Dec 2022 23:14 +00:00:
> On Mon, Dec 12, 2022 at 5:28 PM Bart Schaefer <schaefer@brasslantern.com>
> wrote:
>
>> On Mon, Dec 12, 2022 at 8:08 AM Philippe Altherr
>> <philippe.altherr@gmail.com> wrote:
>> >
>> > Here is an updated patch to document the ERR_EXIT and ERR_RETURN changes.
>>
>> Thanks.
>>
>> > +      echo "This is printed only since 5.10."
>>
>> For the group:  More likely to be 5.9.1 ?
>>
> 
> Hmm, I think all occurrences of "5.10" could be replaced with "this
> version", which would avoid the problem of knowing what the future version
> number will be.

It would be nice to actually say the version number, to make the
sentence as self-contained as possible.  (People might read that section
after upgrading directly from 5.9 to 5.11, or might want to copy-paste
that sentence into a mailing list post, etc..)

No opinion on what the next release's version number should be.  That
would depend on what changes are in master when we create that release.
For now, I guess you can just put in the text whatever version number you
put in the section's title?  We will presumably proofread that section if we
retitle it.

Cheers,

Daniel


      reply	other threads:[~2022-12-13  3:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 16:06 Philippe Altherr
2022-12-12 16:28 ` Bart Schaefer
2022-12-12 23:14   ` Philippe Altherr
2022-12-13  3:20     ` Daniel Shahaf [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=1246e25a-9ec9-4b02-828d-c94a1a8e5ca1@app.fastmail.com \
    --to=d.s@daniel.shahaf.name \
    --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).