On 9/22/25 11:27 AM, Álvaro Herrera wrote:
On 2025-Sep-22, Tom Lane wrote:
My first thought about scheduling was "best not in the middle of the
18.0 release cycle". However, I don't know of any actual connection
between gitweb/cgit and the release-making tasks. My second thought
was "the poin
On 2025-Sep-22, Tom Lane wrote:
> My first thought about scheduling was "best not in the middle of the
> 18.0 release cycle". However, I don't know of any actual connection
> between gitweb/cgit and the release-making tasks. My second thought
> was "the point here is to cut server load, and mayb
On 9/19/25 4:54 PM, Jonathan S. Katz wrote:
On 9/19/25 4:14 PM, Tom Lane wrote:
"Jonathan S. Katz" writes:
On a quick read, I believe this is easily settable in the cgit.css file
by setting "tab-size" to "4". I did a quick test hacking this inline,
and it worked.
Cool, thanks for looking int
"Jonathan S. Katz" writes:
> If the main concern is lack of diff - which cgit gives us back, and the
> main objection is the tab-size patch (in previous email)[1], is there
> any objection to moving forward with updating the URLs after this patch
> is applied (which I can't do, as I don't have
On 2025-Sep-19, Peter Eisentraut wrote:
> On 19.09.25 03:12, Jonathan S. Katz wrote:
> > * Moves any web links to git.postgresql.org repos to use the cgit
> > interface instead of gitweb (e.g. [1])
> > * Update the commit search[2] to use cgit instead of gitweb
>
> If we're doing that -- which se
On 9/19/25 12:17 PM, Tom Lane wrote:
Peter Geoghegan writes:
cgit messes up indentation by showing 8 space tabs (not 4 space tabs)
-- that's certainly not ideal.
To me that seems like a complete blocker for this proposal,
if we can't find a fix.
On a quick read, I believe this is easily set
On 9/19/25 4:14 PM, Tom Lane wrote:
"Jonathan S. Katz" writes:
On a quick read, I believe this is easily settable in the cgit.css file
by setting "tab-size" to "4". I did a quick test hacking this inline,
and it worked.
Cool, thanks for looking into it.
Tested inline, but untested as a whol
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 be
On 9/19/25 7:42 AM, David Rowley wrote:
On Fri, 19 Sept 2025 at 23:05, Peter Eisentraut 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 c
On Thu, Sep 18, 2025 at 9:12 PM Jonathan S. Katz wrote:
> While prepping the website for the PG18 GA, I stumbled on the inability
> to access parts of commits through the gitweb links, specifically
> hitting 429 status code errors (this seems to be intermittent). After
> some briefing on why it's
"Jonathan S. Katz" writes:
> On a quick read, I believe this is easily settable in the cgit.css file
> by setting "tab-size" to "4". I did a quick test hacking this inline,
> and it worked.
Cool, thanks for looking into it.
regards, tom lane
Peter Geoghegan writes:
> cgit messes up indentation by showing 8 space tabs (not 4 space tabs)
> -- that's certainly not ideal.
To me that seems like a complete blocker for this proposal,
if we can't find a fix.
regards, tom lane
On 9/19/25 10:47 AM, Álvaro Herrera wrote:
On 2025-Sep-19, Peter Eisentraut wrote:
On 19.09.25 03:12, Jonathan S. Katz wrote:
* Moves any web links to git.postgresql.org repos to use the cgit
interface instead of gitweb (e.g. [1])
* Update the commit search[2] to use cgit instead of gitweb
I
On Fri, 19 Sept 2025 at 23:05, Peter Eisentraut 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 java
> On 19 Sep 2025, at 13:05, Peter Eisentraut 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 javascrip
On 19.09.25 03:12, Jonathan S. Katz wrote:
* Moves any web links to git.postgresql.org repos to use the cgit
interface instead of gitweb (e.g. [1])
* Update the commit search[2] to use cgit instead of gitweb
If we're doing that -- which seems reasonable -- then perhaps also
update the forward
On 2025-Sep-19, David Rowley wrote:
> You didn't mention the cause of the specific issues, but it has been
> mentioned on www lists before, so I don't think it's a secret with the
> bot traffic. Have you considered if switching these links to cgit
> wouldn't just cause the traffic to migrate to c
Hi,
While prepping the website for the PG18 GA, I stumbled on the inability
to access parts of commits through the gitweb links, specifically
hitting 429 status code errors (this seems to be intermittent). After
some briefing on why it's disabled and how this isn't an issue with
cgit, I prepp
On Fri, 19 Sept 2025 at 13:12, Jonathan S. Katz wrote:
> While prepping the website for the PG18 GA, I stumbled on the inability
> to access parts of commits through the gitweb links, specifically
> hitting 429 status code errors (this seems to be intermittent). After
> some briefing on why it's d
19 matches
Mail list logo
