> Am 04.02.2015 um 00:20 schrieb Andreas Schwab :
>
> Jonny Grant writes:
>
>> How many minutes labor is this task?
>
> What does it fix?
How many hacks/workarounds can be avoided?
> Am 01.02.2015 um 17:09 schrieb Eli Zaretskii :
>
>> Date: Sat, 31 Jan 2015 01:55:29 +
>> From: Jonathan Wakely
>> Cc: Andrew Pinski , "gcc@gcc.gnu.org" ,
>> Jonny Grant
>>
>> These files are only compiled by GCC's own build system, with GCC's
>> own makefiles, so we know we invoke the C
> Am 31.01.2015 um 21:21 schrieb DJ Delorie :
>
>
>> Aren't current Windows file systems case-preserving? Then they
>> shouldn't have no problems with .C files.
>
> They are case preserving, but not case sensitive. A wildcard search
> for *.c will match foo.C and bar.c, and foo.c can be opene
> Am 31.01.2015 um 02:57 schrieb Jonathan Wakely :
>
> On 30 January 2015 at 22:24, Kevin Ingwersen (Ingwie Phoenix) wrote:
>> Apple’s HFS is, on a default OS X install, case insensitive.
>
> Which doesn't matter, see my previous reply.
That is true; though its good
> Am 30.01.2015 um 22:39 schrieb DJ Delorie :
>
>
> pins...@gmail.com writes:
>> No because they are c++ code so capital C is correct.
>
> However, we should avoid relying on case-sensitive file systems
> (Windows) and use .cc or .cxx for C++ files ("+" is not a valid file
> name character on
> Am 30.01.2015 um 21:30 schrieb Jonny Grant :
>
>
>
> On 30/01/15 17:09, pins...@gmail.com wrote:
>>
>>
>>
>>
>>> On Jan 30, 2015, at 4:22 AM, Jonny Grant wrote:
>>>
>>> Hello
>>>
>>> When I checked out from the trunk I saw that various files had .C
>>> capital extension. Its not a big
