| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Vik Fearing <vik(at)postgresfriends(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: meson files copyright |
| Date: | 2022-12-19 20:09:25 |
| Message-ID: | 063342bf-cd15-afa9-3099-aa3198636747@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19.12.22 19:33, Robert Haas wrote:
> On Mon, Dec 19, 2022 at 1:03 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Vik Fearing <vik(at)postgresfriends(dot)org> writes:
>>> Perhaps a bit off-topic, but what is the point of the file identifiers?
>>
>> IMO, it helps to tell things apart when you've got a bunch of editor
>> windows open on some mighty samey-looking meson.build files.
>
> On the other hand, maintaining those identification lines in all of
> our files has a pretty high distributed cost. I never use them to
> figure out what file I'm editing because my editor can tell me that.
> But I do have to keep fixing those lines as I create new files. It's
> not the most annoying thing ever, but I wouldn't mind a bit if I
> didn't have to do it any more.
I agree it's not very useful and a bit annoying.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-12-19 20:23:09 | Re: appendBinaryStringInfo stuff |
| Previous Message | Peter Eisentraut | 2022-12-19 20:08:54 | Re: Fixing typo in 002_pg_dump.pl |