From: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: 4.0.2 imminent
Date: Mon, 25 Jun 2001 21:38:53 +0400 (MSD) [thread overview]
Message-ID: <Pine.SV4.4.33.0106252136200.19240-100000@itsrm2.mow.siemens.ru> (raw)
In-Reply-To: <Tc0a88d01545d30906e@mailsweeper01.cambridgesiliconradio.com>
On Mon, 25 Jun 2001, Peter Stephenson wrote:
> Note it will be configured using autoconf 2.13 for consistency, although
> 2.50 is supported if you are building from scratch. I plan to use 2.50 for
> public versions starting with development releases of 4.1 (there will
> probably be one of those soon).
>
Yes. Using 2.50 means new parameters for configure (just to mention -C for
caching), and obsolete --enable-{libs,cflags,ldflags} that means, README
should be changed as well and it is too much already.
-andrej
prev parent reply other threads:[~2001-06-25 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 17:03 Peter Stephenson
2001-06-25 17:38 ` Andrej Borsenkow [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=Pine.SV4.4.33.0106252136200.19240-100000@itsrm2.mow.siemens.ru \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=zsh-workers@sunsite.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).