From: Eitan Adler <lists@eitanadler.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: MACHINES, FEATURES, etc.
Date: Thu, 31 May 2018 23:14:41 -0700 [thread overview]
Message-ID: <CAF6rxg=6BTVv+DpkCO0mFtWYouY+QFxWuZtnVtRcjnZouib+6w@mail.gmail.com> (raw)
In-Reply-To: <20180530135204eucas1p1a7c9c765123d0998d52e60816a3ebb96~zcG-h1udK1559415594eucas1p17@eucas1p1.samsung.com>
On 30 May 2018 at 06:52, Peter Stephenson <p.stephenson@samsung.com> wrote:
> On Wed, 30 May 2018 09:45:11 -0400
> Vin Shelton <acs@alumni.princeton.edu> wrote:
>> I spotted a minor typo: comiple. Also, I recommend including a date
>> to give more substance to the phrase: "At the time of writing".
>
> Thanks for the sanity check --- I've included a version as well as a date.
> I search for the previous version globally when updating so the
> last release is probably the right thing to put.
>
> pws
>
>
> -----------------------------
> ZSH ON SPECIFIC ARCHITECTURES
> -----------------------------
>
> This file is to record difficulties in compiling and installing zsh on
> specific architectures.
>
> The information in this list may be out of date, as the developers do
> not have access to all machines. In general, GNU/Linux distributions
> and BSD derivatives including MacOS are reasonably well covered.
>
> At the time of writing (2018/05/30, version 5.5.1) zsh is believed to
> compile on all up-to-date Unix-like operating systems. Please let us
> know of any exceptions.
LGTM.
--
Eitan Adler
prev parent reply other threads:[~2018-06-01 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180527065011epcas4p11a700ef0b52cf84d167ed3a02b5560d8@epcas4p1.samsung.com>
2018-05-27 6:49 ` Eitan Adler
2018-05-29 8:34 ` Peter Stephenson
[not found] ` <20180529093455.6e884257@camnpupstephen.cam.scsc.local>
2018-05-30 13:26 ` Peter Stephenson
2018-05-30 13:45 ` Vin Shelton
2018-05-30 13:52 ` Peter Stephenson
2018-06-01 6:14 ` Eitan Adler [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='CAF6rxg=6BTVv+DpkCO0mFtWYouY+QFxWuZtnVtRcjnZouib+6w@mail.gmail.com' \
--to=lists@eitanadler.com \
--cc=p.stephenson@samsung.com \
--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).