Re: .gitignore for some of cygwin files

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Radosław Smogura <rsmogura(at)softperience(dot)eu>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: .gitignore for some of cygwin files
Date: 2011-06-09 14:22:42
Message-ID: BANLkTimFd=XeQXY6ueAmNtm5oQPvEdZn8w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 9, 2011 at 15:40, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>
> On 06/09/2011 08:12 AM, Magnus Hagander wrote:
>>
>> On Wed, Jun 8, 2011 at 12:34, Radosław Smogura<rsmogura(at)softperience(dot)eu>
>>  wrote:
>>>
>>> After compilation I got big list of differences about binaries and other
>>> files. You may see it in patch.
>>
>> Hmm. Does this really affect just cygwin, and not also mingw?
>
> Yes, indeed.
>
>> I know
>> msvc builds out-of-tree, but mingw doesn't, iirc? WHere do the EXEs go
>> there?
>
>
> The .exe files go exactly where linked executables go on Unix. We could add
> .gitignore lines for them just as we have for Unix, e.g. by adding
> "/initdb.exe" to src/bin/initdb.gitignore, or more simply by adding a global
> rule for "*.exe" as the patch proposes.

I think a global exclude for *.exe makes perfect sense. I don't see
why we would ever want to commit a .exe file to the repository...

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-06-09 14:24:16 Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS
Previous Message Alvaro Herrera 2011-06-09 14:22:23 Re: literature on write-ahead logging