Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
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: Sun, 18 Mar 2001 23:39:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010319093420.21558G-100000@is> (raw)
In-Reply-To: <3AB3CB1D.85E1E043@cygnus.com>

On Sat, 17 Mar 2001, Andrew Cagney wrote:

> Per discussion on the gdb@ list, this patch moves GDB's version number
> out of Makefile.in and into a separate file called (of all things :-)
> VERSION.

This will get us back into the nuisance we had with COPYING and
copying.c, due to the file-name letter-case nuisance on DOS/Windows
file systems.  See this ChangeLog entry:

  2000-04-03  Eli Zaretskii  <eliz@is.elta.co.il>

          * Makefile.in (copying.c): Depend on copying.txt, not COPYING.
          (copying.txt): New target, a link to COPYING.

Can we have a different name, please?  Why can't we have version.c in
the first place, without any intermediaries?  COPYING was an external
file, but VERSION is not, I believe.


  reply	other threads:[~2001-03-18 23:39 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 [this message]
     [not found] ` <3AFB1C97.30009@cygnus.com>
2001-05-10 18:26   ` Andrew Cagney
     [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=Pine.SUN.3.91.1010319093420.21558G-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=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