This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Ada: ^M in ada source files

From: Robert Dewar <dewar at adacore dot com>
To: Mike Stump <mikestump at comcast dot net>
Cc: "gcc-patches at gcc dot gnu dot org Patches" <gcc-patches at gcc dot gnu dot org>
Date: Fri, 07 Dec 2012 14:43:22 -0500
Subject: Re: Ada: ^M in ada source files
References: <17DD7D78-69AA-4CE3-B3BC-5EDE05986D8E@comcast.net> <50C23C24.9060402@adacore.com> <D0E12E74-070E-4123-9BF6-7ED1D4235E11@comcast.net>

On 12/7/2012 2:09 PM, Mike Stump wrote:

On Dec 7, 2012, at 10:57 AM, Robert Dewar <dewar@adacore.com> wrote:
On 12/7/2012 1:56 PM, Mike Stump wrote:
I've noticed that:
$ grep -l '^M' gcc/testsuite/gnat.dg/*
discr36.ads
discr36_pkg.adb
discr36_pkg.ads
discr38.adb
loop_optimization11.adb
loop_optimization11_pkg.ads
loop_optimization13.adb
loop_optimization13.ads
:-( Surely these are just normal text files, right? Can I strip the ^M from them?
Probably good to have some tests with standard CR/LF terminators, since this is what a lot of the world uses.
Then, to preserve them, the files must be tagged as binary in svn and git. Doing so will probably make the normal file merging that git/svn would do, inoperative.

Ok to so tag all the files?

probably not worth it if it causes that disruption. svn certainly handleds CR/LF terminators fine, I guess Git does not?

Follow-Ups:
- Re: Ada: ^M in ada source files
  - From: Arnaud Charlet

References:
- Ada: ^M in ada source files
  - From: Mike Stump
- Re: Ada: ^M in ada source files
  - From: Robert Dewar
- Re: Ada: ^M in ada source files
  - From: Mike Stump

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]