pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Docs after split
2+ messages / 2 participants
[nested] [flat]

* Docs after split
@ 2000-05-27 03:30  Bruce Momjian <pgman@candle.pha.pa.us>
  0 siblings, 1 reply; 2+ messages in thread

From: Bruce Momjian @ 2000-05-27 03:30 UTC (permalink / raw)
  To: Thomas G. Lockhart <lockhart@alumni.caltech.edu>; +Cc: PostgreSQL-documentation <docs@postgresql.org>

Thomas, now that there is a 7.0 split, do you want to keep both cvs
trees up-to-date, or just keep current up-to-date?

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Docs after split
@ 2000-05-31 02:18  Thomas Lockhart <lockhart@alumni.caltech.edu>
  parent: Bruce Momjian <pgman@candle.pha.pa.us>
  0 siblings, 0 replies; 2+ messages in thread

From: Thomas Lockhart @ 2000-05-31 02:18 UTC (permalink / raw)
  To: Bruce Momjian <pgman@candle.pha.pa.us>; +Cc: PostgreSQL-documentation <docs@postgresql.org>

> Thomas, now that there is a 7.0 split, do you want to keep both cvs
> trees up-to-date, or just keep current up-to-date?

current should be supported for sure. Haven't bothered with the stable
tree, since it could lead to a large increase in work.

istm that we *could* update the stable branch at the last minute by
diffing two trees.

                      - Thomas



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2000-05-31 02:18 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-05-27 03:30 Docs after split Bruce Momjian <pgman@candle.pha.pa.us>
2000-05-31 02:18 ` Thomas Lockhart <lockhart@alumni.caltech.edu>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox