Re: Couple of patches for jdbc driver - Mailing list pgsql-jdbc

From Ned Wolpert
Subject Re: Couple of patches for jdbc driver
Date
Msg-id XFMail.20010821122233.ned.wolpert@knowledgenet.com
Whole thread Raw
In response to Couple of patches for jdbc driver  (Ned Wolpert <ned.wolpert@knowledgenet.com>)
Responses Re: Couple of patches for jdbc driver  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Couple of patches for jdbc driver  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-jdbc
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I guess my question is, when I submitted the patches after 7.1.2 was released,
I was hoping they would be in the next release, 7.1.3  Is there a way for my
patches to make it into the next release, which I assume is 7.2?  Or, is the
current source-tree geared for 7.2 all-along?

On 21-Aug-2001 Tom Lane wrote:
> Ned Wolpert <ned.wolpert@knowledgenet.com> writes:
>> (You patched this about two months ago.)  Specifically, the 1.11 version of
>> jdbc2/PreparedStatment.java file has the patch, but the 7.1.3 released does
>> not.  How do we propragate patches into the main branch for releasing?
>
> At this point, we don't; it's quite unlikely that there will be a 7.1.4,
> considering that we hope to be in 7.2 beta within a month.
>
> As far as JDBC goes, lots of people seem to be using CVS snapshots quite
> happily, so I'm not sure an official back-patch is needed anyway.
>
>                       regards, tom lane


Virtually,
Ned Wolpert <ned.wolpert@knowledgenet.com>

D08C2F45:  28E7 56CB 58AC C622 5A51  3C42 8B2B 2739 D08C 2F45
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7grT5iysnOdCML0URAjg3AJ9Zb45j8askvzCw4KeJes4Tx6zDSQCffcE7
HgvGPQt1/OnREkzSfG4AS90=
=vUv3
-----END PGP SIGNATURE-----

pgsql-jdbc by date:

Previous
From: Ned Wolpert
Date:
Subject: Re: Couple of patches for jdbc driver
Next
From: Tom Lane
Date:
Subject: Re: Couple of patches for jdbc driver