From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Commit fest 2017-01 will begin soon! |
Date: | 2017-02-13 03:25:09 |
Message-ID: | 389992ae-365d-07ce-e819-df36a0c8870c@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/1/17 10:39 PM, Michael Paquier wrote:
> On Thu, Feb 2, 2017 at 1:23 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>> Many thanks to you for running the show. I think it might be okay if
>> one consolidated mail is sent for all the patches that are marked
>> "Returned with Feedback" or "Rejected" or "Moved to next CF". OTOH,
>> there is some value in sending a separate mail for each patch so that
>> people can argue on the decision by CFM for one particular patch, but
>> not sure if it worth.
>
> People tend to look at emails they are directly on in CC, that's why I
> prefer sending individual emails.
BTW, the app also sends email notifications to anyone named on a patch
(or at least I got notifications). Having a human spend time doing that
by hand seems pretty silly.
Since the app also knows about the email threads, presumably it could
send notifications to relevant threads as well.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
From | Date | Subject | |
---|---|---|---|
Next Message | Okano, Naoki | 2017-02-13 04:12:50 | Keep ECPG comment for log_min_duration_statement |
Previous Message | Jim Nasby | 2017-02-13 03:21:16 | Re: Time to up bgwriter_lru_maxpages? |