Re: meson files copyright

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-20 17:25:24
Message-ID: 20221220172524.gejjifypqx5fhuyp@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022-12-19 13:33:46 -0500, 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.

+1

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-12-20 17:29:58 Re: meson and tmp_install
Previous Message Tom Lane 2022-12-20 16:12:09 Re: Use get_call_result_type() more widely