Re: [PATCHES] pglister: make organization name generic - Mailing list pgsql-www

From Célestin Matte
Subject Re: [PATCHES] pglister: make organization name generic
Date
Msg-id a37e411a-d387-2202-2d98-6b4d68326247@cmatte.me
Whole thread Raw
In response to Re: [PATCHES] pglister: make organization name generic  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [PATCHES] pglister: make organization name generic  (Magnus Hagander <magnus@hagander.net>)
List 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
sameemail. 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
previousones, 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
spottedthat 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

pgsql-www by date:

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