From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: Getting the CVS revision of Zsh
Date: Tue, 13 Jan 2009 10:09:13 +0000 [thread overview]
Message-ID: <20090113100913.3f27795b@news01> (raw)
In-Reply-To: <a0600100ac591d5879871@kba.biglobe.ne.jp>
On Tue, 13 Jan 2009 14:25:11 +0900
"Jun T." <takimoto-j@kba.biglobe.ne.jp> wrote:
> At 20:13 +0000 09.1.9, Peter Stephenson wrote:
> > +patchlevel.h: $(sdir_top)/ChangeLog
> > + { \
> > + echo -n "#define ZSH_PATCHLEVEL "; \
>
> This does not work on MacOSX 10.5 (Leopard), because sh's builtin
> echo does not accept the option '-n':
OK, how about
Index: Src/zsh.mdd
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/zsh.mdd,v
retrieving revision 1.20
diff -u -r1.20 zsh.mdd
--- Src/zsh.mdd 9 Jan 2009 20:31:23 -0000 1.20
+++ Src/zsh.mdd 13 Jan 2009 10:08:06 -0000
@@ -42,11 +42,9 @@
echo '#define ZSH_VERSION "'$(VERSION)'"' > $@
patchlevel.h: $(sdir_top)/ChangeLog
- { \
- echo -n "#define ZSH_PATCHLEVEL "; \
- sed -ne 's/^\* *\$$''Revision: \(.*\) ''\$$/"\1"/p' \
- $(sdir_top)/ChangeLog; \
- } >patchlevel.h
+ sed -ne \
+ 's/^\* *\$$''Revision: \(.*\) ''\$$/#define ZSH_PATCHLEVEL "\1"/p' \
+ $(sdir_top)/ChangeLog >patchlevel.h
zshcurses.h: ../config.h
@if test x$(ZSH_CURSES_H) != x; then \
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
next prev parent reply other threads:[~2009-01-13 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2d460de70901090301h6b309a7cm19c5ebfec989ff2c@mail.gmail.com>
[not found] ` <200901091121 .n09BLVvZ006382@news01.csr.com>
[not found] ` <200901091121.n09BLVvZ006382@news01.csr.com>
[not found] ` <2d460de70901090348t3ea9e25fi29a7165ee42ae5e5@mail.gmail.com>
[not found] ` <200901091158.n09BwPii006839@news01.csr.com>
[not found] ` <2d460de7090 1090441i7ef1795bs42ed98fe0f33c9ba@mail.gmail.com>
[not found] ` <200901091258.n09CwS7T007 471@news01.csr.com>
[not found] ` <2d460de70901090441i7ef1795bs42ed98fe0f33c9ba@mail.gmail.com>
[not found] ` <200901091258.n09CwS7T007471@news01.csr.com>
[not found] ` <2d460de70901090507i7c3179e4u1e2def459f214566@mail.gmail.com>
2009-01-09 20:13 ` Peter Stephenson
2009-01-09 22:33 ` Richard Hartmann
2009-01-10 21:43 ` Peter Stephenson
2009-01-13 5:25 ` Jun T.
2009-01-13 10:09 ` Peter Stephenson [this message]
2009-01-14 3:48 ` Jun T.
[not found] ` <2d460de70901140533icf13f94yc7f63f974b236f45@mail.gmail.com>
[not found] ` <090114085737.ZM18662@torch.brasslantern.com>
2009-01-14 17:22 ` Peter Stephenson
2009-01-14 23:36 ` Clint Adams
2009-01-15 14:38 ` Peter Stephenson
2009-01-14 18:54 ` Mikael Magnusson
2009-01-15 19:43 ` Peter Stephenson
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=20090113100913.3f27795b@news01 \
--to=pws@csr.com \
--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).