2011/2/1 Magnus Hagander <magnus(at)hagander(dot)net>:
> On Tue, Feb 1, 2011 at 07:56, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> 2011/2/1 Magnus Hagander <magnus(at)hagander(dot)net>:
>>> On Tue, Feb 1, 2011 at 05:53, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>>>> There are broken links inside messages from commiters.
>>>> projects /
>>>> 404 - No such project
>>> Are you using gmail? They have made some changes recently that breaks
>>> the viewing of the URLs. Haven't heard any non-gmail user complain,
>>> and not entirely sure how to fix it. a workaround is to use "copy link
>>> location" or whatever it's called in your browser and then paste that
>>> - that works without errors.
>> yes, you has true. It's gmail bug.
> I'm actually not entirely sure it's a gmail bug - it looks more like
> it's at least partially gitweb's fault, but I'm not entirely sure...
Hgweb (the Mercurial equivalent of gitweb) has the same problem. I
have the impression that the semicolons in the URLs are initially not
escaped correctly or something. Both hgweb and gitweb use semicolons
in the URL; hgweb shows "no such method: changeset;node=69b90bdd52d1"
when following such a "...?cmd=changeset;node=69b90bdd52d1" link from
GMail (using Chrome, in case that matters).
Workaround: When I press enter on the URL in the address bar while the
404 is showing, the page reloads correctly without 404-ing.
In response to
pgsql-hackers by date
|Next:||From: Tom Lanyon||Date: 2011-02-01 10:32:47|
|Subject: out of memory during COPY .. FROM|
|Previous:||From: Magnus Hagander||Date: 2011-02-01 10:01:46|
|Subject: Re: pg_upgrade fails for non-postgres user|