From: Nemeth Ervin <airwin@inf.bme.hu>
To: zsh-users@sunsite.auc.dk
Subject: Stable?
Date: 29 May 2000 10:15:51 +0200 [thread overview]
Message-ID: <gmvsnv1srew.fsf@kempelen.iit.bme.hu> (raw)
Hi,
I don't want to look impatient, but when will 3.1 become stable? 3.0 is
getting 4-years old.
Just because most answers in zsh-users contain: "3.1 already has this
feature", "you can do it by ..., but in 3.1 it is more simple: ..." and so on.
--
Ervin
"Natura unum os et duas aures nobis dedit, quasi admoneret, ut multa
audiremus et pauca diceremus."
next reply other threads:[~2000-05-29 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-29 8:15 Nemeth Ervin [this message]
2000-05-29 8:19 ` Stable? jarausch
2000-05-29 8:51 ` Stable? Nemeth Ervin
2000-05-29 8:58 ` Stable? Bart Schaefer
2000-05-29 16:21 ` Stable? James Kirkpatrick
2000-05-29 18:01 ` Stable? Bart Schaefer
2000-05-30 6:50 ` Stable? Nemeth Ervin
2000-05-30 7:24 ` Stable? Bart Schaefer
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=gmvsnv1srew.fsf@kempelen.iit.bme.hu \
--to=airwin@inf.bme.hu \
--cc=zsh-users@sunsite.auc.dk \
/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).