Re: [PATCHES] pglister: make organization name generic

From: Célestin Matte <celestin(dot)matte(at)cmatte(dot)me>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCHES] pglister: make organization name generic
Date: 2021-11-04 11:21:09
Message-ID: a37e411a-d387-2202-2d98-6b4d68326247@cmatte.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

> As a general rule, please post the patches no the thread of the description, and if it's more than one patch, in the same email. Right now the only thing I see to review is this description, that's kind of hard.

Sorry, I don't understand: should I send all patches by responding to the description email (instead of replying to the previous ones, as I did here), or all patches in the same email?

> As for reviewing the general idea, I agree with that -- makes perfect sense to do that. I did note that Alvaro spotted that it also needs to look over all the rest of the text and find similar stuff -- like the image alt="" attribute. There may be more of those?

Yep, added handling of ORGANIZATION_MOTTO in the set of patches attached to this email.

--
Célestin Matte

Attachment Content-Type Size
0001-Add-orgname-tag-and-settings-to-define-organization-.patch text/x-patch 1.7 KB
0002-Use-orgname-in-templates-to-make-them-organization-g.patch text/x-patch 5.3 KB
0003-Update-banner-images-to-remove-mentions-of-PostreSQL.patch text/x-patch 19.5 KB

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2021-11-04 11:50:01 Re: [PATCH] pglister: load_subscribers.py: don't wait for user input when there is nothing to commit
Previous Message Magnus Hagander 2021-11-04 10:35:41 Re: [PATCH] pgarchives: parser: handle messages in which Message-ID is missing