| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | "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:05:19 |
| Message-ID: | b88c76d0-bf71-43aa-8bfe-7a07f82766da@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2025-09-19 11:08:53 | Re: Having postgresql.org link to cgit instead of gitweb |
| Previous Message | Peter Eisentraut | 2025-09-19 11:04:15 | Re: Having postgresql.org link to cgit instead of gitweb |