Re: meson files copyright - Mailing list pgsql-hackers

From Noah Misch
Subject Re: meson files copyright
Date
Msg-id 20221220052650.GE1086702@rfd.leadboat.com
Whole thread Raw
In response to Re: meson files copyright  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: meson files copyright  (Andrew Dunstan <andrew@dunslane.net>)
Re: meson files copyright  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
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.



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Force streaming every change in logical decoding
Next
From: Peter Eisentraut
Date:
Subject: Re: Common function for percent placeholder replacement