zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Zsh Hackers' List <zsh-workers@sunsite.dk>
Subject: Re: Getting the CVS revision of Zsh
Date: Thu, 15 Jan 2009 19:43:48 +0000	[thread overview]
Message-ID: <20090115194348.55b8c86b@pws-pc> (raw)
In-Reply-To: <237967ef0901141054y35a4fafdpade3134bc49f69aa@mail.gmail.com>

On Wed, 14 Jan 2009 19:54:02 +0100
Mikael Magnusson <mikachu@gmail.com> wrote:
> FWIW, I use a git import which doesn't do any keyword expansion, so
> the define is empty in my case, which obviously breaks the build. I
> don't know if you want to a) not care b) add some #ifdef to set it to
> "unknown" or such or c) add some shell code for git to set it.
> 
> If b or c I can construct a patch.

If keyword expansion is properly turned off it shouldn't remove the CVS
one, although I don't know the details of how git works.  The second
option is probably the easiest; it's straightforward now sed outputs the
entire line, so the definition is completely missing if not found.

Index: Src/params.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/params.c,v
retrieving revision 1.153
diff -u -r1.153 params.c
--- Src/params.c	15 Jan 2009 14:49:51 -0000	1.153
+++ Src/params.c	15 Jan 2009 19:42:36 -0000
@@ -35,6 +35,11 @@
 #define ZSH_PATCHLEVEL	CUSTOM_PATCHLEVEL
 #else
 #include "patchlevel.h"
+
+/* If removed from the ChangeLog for some reason */
+#ifndef ZSH_PATCHLEVEL
+#define ZSH_PATCHLEVEL "unknown"
+#endif
 #endif
 
 /* what level of localness we are at */

-- 
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/


      reply	other threads:[~2009-01-15 19:44 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
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 [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=20090115194348.55b8c86b@pws-pc \
    --to=p.w.stephenson@ntlworld.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).