From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Erik Rijkers <er(at)xs4all(dot)nl> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: commitfest html - wrong closing tag |
Date: | 2016-01-03 10:06:50 |
Message-ID: | CABUevEx74iRL1ypGHRQT8e7uZhkz8ZkMPf+=8_bH5-CppmWMuw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Jan 3, 2016 at 9:26 AM, Erik Rijkers <er(at)xs4all(dot)nl> wrote:
> Hi,
>
> I noticed (trying to parse out the "Latest patch" urls) that
> in the html of the commitfest pages, for instance in:
>
> https://commitfest.postgresql.org/8/
>
> all rows of the html-table (I think it is the "Committer"-column) contain
> an erroneous '</p>'. It should be '</td>'.
>
> See example below, the '<td></p>' should obviously be '<td></td>'.
>
> Browsers don't seem to mind (and I can easily "parse around" it) but maybe
> it can be fixed?
>
That is indeed obviously wrong. Fixed and deployed. (
http://git.postgresql.org/gitweb/?p=pgcommitfest2.git;a=commitdiff;h=3d583f3fb0184b4858395a385438e4cb22080612
)
Is there a particular thing you're trying to parse the data out for? As in
is there some data that we should already be providing in a structured
format instead of requiring parsing it out?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Rijkers | 2016-01-03 10:25:51 | Re: commitfest html - wrong closing tag |
Previous Message | Andreas Karlsson | 2016-01-03 09:36:14 | \x auto and EXPLAIN |