| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, David Rowley <dgrowleyml(at)gmail(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Having postgresql.org link to cgit instead of gitweb |
| Date: | 2025-09-19 11:08:53 |
| Message-ID: | ACBF5486-8A4F-4A03-A48C-2D639B51EDD8@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 19 Sep 2025, at 13:05, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> On 19.09.25 10:22, Álvaro Herrera wrote:
>> There are two things we could do. One is to simply restrict `git blame`
>> to authenticated users; this shouldn't be_too_ bad. But if we don't
>> want that, we could put the bot checker javascript tricks in front of
>> `blame`. In fact maybe we could have the best of both worlds: you get
>> the javascript check if you're not authenticated, but nothing if you
>> are. I'm not sure how easy it is to implement this though.
>
> Or just disable git blame. Who needs to run that through the website?
We could jut link to the postgres mirror on Github for that.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2025-09-19 11:14:37 | Re: Fix typo in comment of match_orclause_to_indexcol() |
| Previous Message | Peter Eisentraut | 2025-09-19 11:05:19 | Re: Having postgresql.org link to cgit instead of gitweb |