From: Thomas Lockhart <lockhart@alumni.caltech.edu>
To: Pierce Tyler <pierce@greatbridge.com>
To: pgsql-docs@postgresql.org
Cc: lockhart@fourpalms.org
Subject: Re: pg_dump
Date: Tue, 27 Feb 2001 00:56:05 +0000
Message-ID: <3A9AFB25.B2131A9B@alumni.caltech.edu> (raw)
References: <3A9AD604.85EDD353@greatbridge.com>
> Noticed a couple of typos in the pg_dump docs (Reference Guide).
> Suggested corrections attached.
Got it. Thanks.
Peter E and other doc'ers:
While there, I noticed that there were some embedded ^M's at the end of
some lines of text. I have a utility to scrub that cruft off of the end
of lines (it scrubs any non-printable character and any whitespace) and
have run it on all of the ref/ files; some had ^M's and others had some
other kind of whitespace stripped out. Most files got touched.
I'd like to commit these at some point, but perhaps I should wait until
freezing the docs? Which btw is Real Soon Now, since scrappy may be
close to declaring the release date.
Comments?
- Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: lockhart@alumni.caltech.edu, pierce@greatbridge.com, lockhart@fourpalms.org
Subject: Re: pg_dump
In-Reply-To: <3A9AFB25.B2131A9B@alumni.caltech.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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