Re: meson files copyright - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: meson files copyright
Date
Msg-id 570bbd1c-f3f8-27c5-77d7-2a65777c16b4@dunslane.net
Whole thread Raw
In response to Re: meson files copyright  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On 2022-12-20 Tu 00:26, Noah Misch wrote:
> On Mon, Dec 19, 2022 at 09:09:25PM +0100, Peter Eisentraut wrote:
>> On 19.12.22 19:33, Robert Haas wrote:
>>> On Mon, Dec 19, 2022 at 1:03 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>>> Vik Fearing <vik@postgresfriends.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.
> Agreed.  To me, it's just one more thing to get wrong.


OK, I think there are enough objections that we can put that aside for
now, I will just go and add the copyright notices.


cheers


andew

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




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: meson and tmp_install
Next
From: Bharath Rupireddy
Date:
Subject: Re: Add LSN along with offset to error messages reported for WAL file read/write/validate header failures