HISTORY fixes

Your patch has been added to the PostgreSQL unapplied patches list at:

http://candle.pha.pa.us/cgi-bin/pgpatches

I will try to apply it within the next 48 hours.

---------------------------------------------------------------------------

Neil Conway wrote:

This patch fixes a few grammatical errors, removes some duplicate
entries, and attributes some JDBC changes to the right people.

Please apply for 7.3.

Cheers,

Neil

P.S. Rather than updating HISTORY in one go before we make a release,
what does everyone think of the idea of updating HISTORY whenver a
patch that makes a user-visible change is committed?

--
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC

[ Attachment, skipping... ]

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Neil Conway <neilc@samurai.com> writes:

P.S. Rather than updating HISTORY in one go before we make a release,
what does everyone think of the idea of updating HISTORY whenver a
patch that makes a user-visible change is committed?

Peter already set up a convention for that: patch the short list near
the front of doc/src/sgml/release.sgml.

HISTORY is a derived file, really; you should be patching release.sgml
I think, not HISTORY.

regards, tom lane

Tom Lane wrote:

Neil Conway <neilc@samurai.com> writes:

P.S. Rather than updating HISTORY in one go before we make a release,
what does everyone think of the idea of updating HISTORY whenver a
patch that makes a user-visible change is committed?

Peter already set up a convention for that: patch the short list near
the front of doc/src/sgml/release.sgml.

HISTORY is a derived file, really; you should be patching release.sgml
I think, not HISTORY.

Just a clarification. If you are changing 7.3 stuff, /HISTORY is the
place to do it. If it is prior releases, release.sgml is the place, and
when Peter regenerates HISTORY as part of the final release, /HISTORY is
updated. This is easy to figure out because release.sgml doesn't have
info in it for 7.3 yet.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Patch applied. Thanks.

---------------------------------------------------------------------------

Neil Conway wrote:

This patch fixes a few grammatical errors, removes some duplicate
entries, and attributes some JDBC changes to the right people.

Please apply for 7.3.

Cheers,

Neil

P.S. Rather than updating HISTORY in one go before we make a release,
what does everyone think of the idea of updating HISTORY whenver a
patch that makes a user-visible change is committed?

--
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC

[ Attachment, skipping... ]

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073