From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Sayyid Ali Sajjad Rizavi <sasrizavi(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] Add .idea to gitignore for JetBrains CLion |
Date: | 2022-12-04 20:02:04 |
Message-ID: | 08AE3148-3BA1-41C3-B598-4401C58E0EBA@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 4 Dec 2022, at 16:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Sayyid Ali Sajjad Rizavi <sasrizavi(at)gmail(dot)com> writes:
>> +**/.idea
>
> Our policy is that the in-tree .gitignore files should only hide
> files that are build artifacts of standard build processes.
> Something like this belongs in your personal ~/.gitexclude,
> instead.
Since this comes up every now and again, I wonder if it's worth documenting
this in our .gitignore along the lines of:
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,7 @@
+# This contains ignores for build artifacts from standard builds,
+# auxiliary files from local workflows should be ignored locally
+# with $GIT_DIR/info/exclude
+
> (BTW, perhaps we should remove the entries targeting ".sl"
> extensions? AFAIK that was only for HP-UX, which is now
> desupported.)
+1. Grepping through the .gitignores in the tree didn't reveal anything else
that seemed to have outlived its usefulness.
--
Daniel Gustafsson https://vmware.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-12-04 20:14:04 | Re: [PATCH] Add .idea to gitignore for JetBrains CLion |
Previous Message | Justin Pryzby | 2022-12-04 19:09:35 | Re: CREATE INDEX CONCURRENTLY on partitioned index |