Re: Weird mangling of a commit log entry in gitweb summary

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-www(at)lists(dot)postgresql(dot)org
Subject: Re: Weird mangling of a commit log entry in gitweb summary
Date: 2022-07-18 08:37:16
Message-ID: 20220718083716.3nc3gdxwexkfhvsi@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Mon, Jul 18, 2022 at 10:27:47AM +0200, Magnus Hagander wrote:
>
> AFAICT this is not functionality that can be turned off, it's all
> hardcoded both in what it searches and when it does it. :/
>
> I doubt it's worth forking and maintaining a fork just to handle this
> situation given how seldom it shows up.

+1, especially since it was introduced 17 years ago and this is probably the
first time someone notice it in our instance.

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Joe Conway 2022-07-18 13:09:56 Re: Wiki editor request
Previous Message Magnus Hagander 2022-07-18 08:27:47 Re: Weird mangling of a commit log entry in gitweb summary