Re: Ignore Visual Studio's Temp Files While Working with PG on Windows

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>, Yasir <yasir(dot)hussain(dot)shah(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Ignore Visual Studio's Temp Files While Working with PG on Windows
Date: 2024-05-18 14:24:04
Message-ID: 82c4389c-8e94-42af-bc9f-3b8d5f5d8d4e@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers


On 2024-05-17 Fr 02:34, Peter Eisentraut wrote:
> On 17.05.24 08:09, Yasir wrote:
>> I have been playing with PG on the Windows platform recently. An
>> annoying thing I faced is that a lot of Visual Studio's temp files
>> kept appearing in git changed files. Therefore, I am submitting this
>> very trivial patch to ignore these temp files.
>
> Our general recommendation is that you put such things into your
> personal global git ignore file.
>
> For example, I have in ~/.gitconfig
>
> [core]
>         excludesFile = ~/.gitexcludes
>
> and then in ~/.gitexcludes I have various ignores that are specific to
> my local tooling.
>
> That way we don't have to maintain ignore lists for all the tools in
> the world in the PostgreSQL source tree.
>
>
>

or if you want something repo-specific, you can add entries to
.git/info/exclude

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Josef Šimánek 2024-05-18 14:27:41 Re: Ignore Visual Studio's Temp Files While Working with PG on Windows
Previous Message Tom Lane 2024-05-17 15:42:00 pgsql: Sync typedefs.list with buildfarm, for real this time.

Browse pgsql-hackers by date

  From Date Subject
Next Message Josef Šimánek 2024-05-18 14:27:41 Re: Ignore Visual Studio's Temp Files While Working with PG on Windows
Previous Message Martijn Wallet 2024-05-18 14:02:17 Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);