From: "İsmail Dönmez" <ismail@donmez.ws>
To: zsh-workers@zsh.org
Subject: Re: 5.0.2-test-2 is available
Date: Mon, 9 Dec 2013 12:16:47 +0200 [thread overview]
Message-ID: <CAJ1KOAiut=cMAnHpzRwAAtAystp+P9eFpjRrJZi0rtaBQKxW_A@mail.gmail.com> (raw)
In-Reply-To: <20131209101257.1f7974b0@pwslap01u.europe.root.pri>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
Hi,
On Mon, Dec 9, 2013 at 12:12 PM, Peter Stephenson
<p.stephenson@samsung.com>wrote:
> On Mon, 09 Dec 2013 11:53:18 +0200
> İsmail Dönmez <ismail@donmez.ws> wrote:
> > > + ../Util/helpfiles
> > > Usage: helpfiles zshbuiltins.1 dest-dir [link-file]
> >
> > Looks like the following rpm spec file fragment triggers this:
> >
> > # make help text files
> > install -d Help
> > pushd Help/
> > troff -Tlatin1 -t -mandoc ../Doc/zshbuiltins.1 | \
> > grotty -cbou | \
> > sed -e 's/±/{+|-}/' | \
> > ../Util/helpfiles
> > popd
>
> (Moved to zsh-workers.)
>
> That probably ought to be "perl ../Util/helpfiles" to be safe. I think
> the code within the distribution does this OK.
>
Looks like this code is not needed at all now. Doc/help/* seems to provide
the help files already. Thanks a lot! Now only remaining test failure is
the MONITOR thing which is already known.
Regards.
prev parent reply other threads:[~2013-12-09 10:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131201194653.7a98a4a4@pws-pc.ntlworld.com>
[not found] ` <20131202151557.1636@binki>
2013-12-02 16:08 ` Peter Stephenson
2013-12-02 16:36 ` Bart Schaefer
2013-12-02 16:51 ` Peter Stephenson
2013-12-02 17:31 ` Bart Schaefer
2013-12-02 17:40 ` Peter Stephenson
2013-12-08 20:22 ` Peter Stephenson
2013-12-08 21:36 ` Bart Schaefer
2013-12-10 3:21 ` 5.0.2-test-3, arithmetic on pointer to void pda
2013-12-10 6:27 ` Bart Schaefer
2013-12-02 18:08 ` 5.0.2-test-2 is available Bart Schaefer
[not found] ` <20131202155119.GR13790@sym.noone.org>
[not found] ` <20131202160133.7d77d7be@pwslap01u.europe.root.pri>
2013-12-02 16:16 ` Test suite failures on static build (was: 5.0.2-test-2 is available) Axel Beckert
2013-12-02 16:28 ` Peter Stephenson
2013-12-02 16:43 ` Bart Schaefer
2013-12-02 16:48 ` Axel Beckert
2013-12-02 16:57 ` [seems solved] " Axel Beckert
2013-12-02 17:20 ` One test suite failure left on static build (after $HOME has been fixed) Axel Beckert
2013-12-02 17:49 ` Bart Schaefer
[not found] ` <20131202151502.GP13790@sym.noone.org>
2013-12-02 16:28 ` Test suite failures in 5.0.2-test-1 _and_ 5.0.2-test-3 on automatic build (was: Re: 5.0.2-test-2 is available) Axel Beckert
2013-12-02 17:22 ` Bart Schaefer
2013-12-02 18:25 ` Axel Beckert
2013-12-02 18:29 ` Bart Schaefer
2013-12-02 18:34 ` Bart Schaefer
2013-12-03 8:15 ` [SOLVED] " Axel Beckert
[not found] ` <CAJ1KOAj6_KJL59OM_03JhzFLzSJvw_-N8zAeiv94kh7PpNdN0Q@mail.gmail.com>
[not found] ` <CAJ1KOAjJumPnzGWT+sg6-A34Aisp_+PfaCZkP3P8-LDpM7YJhg@mail.gmail.com>
2013-12-09 10:12 ` 5.0.2-test-2 is available Peter Stephenson
2013-12-09 10:16 ` İsmail Dönmez [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='CAJ1KOAiut=cMAnHpzRwAAtAystp+P9eFpjRrJZi0rtaBQKxW_A@mail.gmail.com' \
--to=ismail@donmez.ws \
--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).