Re: Commitfest 2023-03 starting tomorrow!

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Greg Stark <stark(at)mit(dot)edu>, "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Commitfest 2023-03 starting tomorrow!
Date: 2023-03-22 09:39:25
Message-ID: aa89f79f-db78-a8a6-830d-e9af94ea7a7f@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21.03.23 10:59, Alvaro Herrera wrote:
> This led me to suggesting that perhaps we need to be more lenient when
> it comes to new contributors. As I said, for seasoned contributors,
> it's not a problem to keep up with our requirements, however silly they
> are. But people who spend their evenings a whole week or month trying
> to understand how to patch for one thing that they want, to be received
> by six months of silence followed by a constant influx of "please rebase
> please rebase please rebase", no useful feedback, and termination with
> "eh, you haven't rebased for the 1001th time, your patch has been WoA
> for X days, we're setting it RwF, feel free to return next year" ...
> they are most certainly off-put and will*not* try again next year.

Personally, if a patch isn't rebased up to the minute doesn't bother me
at all. It's easy to check out as of when the email was sent (or extra
bonus points for using git format-patch --base). Now, rebasing every
month or so is nice, but daily rebases during a commit fest are almost
more distracting than just leaving it.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2023-03-22 09:42:00 Re: Save a few bytes in pg_attribute
Previous Message Michael Paquier 2023-03-22 09:34:40 Re: Reconcile stats in find_tabstat_entry() and get rid of PgStat_BackendFunctionEntry