Re: JDBC patch procedures (Re: [PATCHES] Patch for jdbc2 ResultSet.java)

From: Rene Pijlman <rene(at)lab(dot)applinet(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-jdbc(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org
Subject: Re: JDBC patch procedures (Re: [PATCHES] Patch for jdbc2 ResultSet.java)
Date: 2001-09-06 19:12:22
Message-ID: tgifpt47mdolruhnurrg6jso097rpbtjqi@4ax.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc pgsql-patches

On Thu, 06 Sep 2001 14:30:49 -0400, you wrote:
>Ultimately it's the committer's responsibility
>to have confidence that the patch he applies is good; if he doesn't
>feel competent to check it himself, he should call for more reviewers.
>If he does feel sure about it, there's no need for procedural overhead.

Agreed. If the committer is in the "team of certified reviewers"
and is willing to review patches, our procedures are basically
the same.

Regards,
René Pijlman <rene(at)lab(dot)applinet(dot)nl>

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Bruce Momjian 2001-09-06 20:07:46 Re: JDBC patch procedures (Re: [PATCHES] Patch for jdbc2 ResultSet.java)
Previous Message chris markiewicz 2001-09-06 18:57:49 Re: error - NOTICE: current transaction...MORE DETAIL...

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2001-09-06 20:07:46 Re: JDBC patch procedures (Re: [PATCHES] Patch for jdbc2 ResultSet.java)
Previous Message Matt Block 2001-09-06 18:33:24 Re: Bug in createlang?