Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: [rfc] Move Makefile.in:VERSION to VERSION file
Date: Thu, 10 May 2001 18:26:00 -0000	[thread overview]
Message-ID: <3AFB3FC9.4030403@cygnus.com> (raw)
In-Reply-To: <3AFB1C97.30009@cygnus.com>

> FYI,  I'm about to check in the below but with s/VERSION/version/ for the file.
> 
> Anyone like to come up with a 5 line /bin/sh script that updates this file using CVS.  It would need to remember to use date -u and should probably check that it hasn't already been run today (1).  The path to the CVS repository and the path to the file would be arguments.
> 
> 
>     Andrew
> 
> (1) Due to the timezone scrample and the possibility of the CVS server going down, I'm thinking of cheating and running the cronjob twice (if not more :-)
> 
> 2001-03-17  Andrew Cagney  <ac131313@redhat.com>
> 
> * Makefile.in (VERSION): Delete.  Moved to file VERSION.
>     (version.c): Depends on file VERSION.  Extract version number from
>     VERSION file.
>     * VERSION: New file.
Not quite.

If the file is called ``version'' then make gets to smart for its self 
and thinks it knows how to build ``version'' from ``version.c'' ...

I'm now trying version.in.

	Andrew



  parent reply	other threads:[~2001-05-10 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-18 14:18 Andrew Cagney
2001-03-18 23:39 ` Eli Zaretskii
     [not found] ` <3AFB1C97.30009@cygnus.com>
2001-05-10 18:26   ` Andrew Cagney [this message]
     [not found] <3AB62D06.55308D3A@cygnus.com>
2001-03-19  9:20 ` Eli Zaretskii
2001-03-19 10:05   ` Andrew Cagney
2001-03-19 11:54     ` Eli Zaretskii
     [not found]       ` <3ABBF966.A0155703@cygnus.com>
2001-03-23 23:58         ` Eli Zaretskii

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=3AFB3FC9.4030403@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox