Re: remove 'noversion' from standalone backend

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: remove 'noversion' from standalone backend
Date: 2004-01-06 18:29:23
Message-ID: 22242.1073413763@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Neil Conway <neilc(at)samurai(dot)com> writes:
> The procedure I'm following is:

> - for trivial / obviously correct patches, just apply them immediately

Check.

> - for fairly simple patches, submit them to the list and apply them
> fairly soon afterward (say, within 24 hours or 48 hours). When I
> apply the patch, send another mail to wrap up the issue.

I think the pgsql-committers log message is sufficient indication that
you did it, and the followup message on -patches is unnecessary.
We usually acknowledge applying patches from non-committers, on the
theory that they might not be subscribed to pgsql-committers. But
for your situation I don't see the value in the extra message.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2004-01-06 18:34:10 Re: remove 'noversion' from standalone backend
Previous Message Alvaro Herrera 2004-01-06 18:28:31 Re: [PATCHES] remove 'noversion' from standalone backend

Browse pgsql-patches by date

  From Date Subject
Next Message Peter Eisentraut 2004-01-06 18:34:10 Re: remove 'noversion' from standalone backend
Previous Message Alvaro Herrera 2004-01-06 18:28:31 Re: [PATCHES] remove 'noversion' from standalone backend