Re: meson files copyright

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: 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 18:33:46
Message-ID: CA+TgmobAZ0LZk1fyuWAfpOD18uF5dMF-32B_FHBq62go+4ARtA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-12-19 18:43:32 Re: Use get_call_result_type() more widely
Previous Message Robert Haas 2022-12-19 18:25:19 Re: Error-safe user functions