Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1R2dDx60706 for ; Mon, 26 Feb 2001 21:39:13 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f1R2d7927585; Mon, 26 Feb 2001 21:39:07 -0500 (EST) To: lockhart@fourpalms.org cc: Pierce Tyler , pgsql-docs@postgresql.org Subject: Re: Re: pg_dump In-reply-to: <3A9AFB25.B2131A9B@alumni.caltech.edu> References: <3A9AD604.85EDD353@greatbridge.com> <3A9AFB25.B2131A9B@alumni.caltech.edu> Comments: In-reply-to Thomas Lockhart message dated "Tue, 27 Feb 2001 00:56:05 +0000" Date: Mon, 26 Feb 2001 21:39:07 -0500 Message-ID: <27582.983241547@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/164 X-Sequence-Number: 424 Thomas Lockhart writes: > While there, I noticed that there were some embedded ^M's at the end of > some lines of text. Yeah, I'd griped about that a month or so back, but didn't get around to doing something about it. > 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? I'd say commit now, else you'll have to redo the work later. I think we are still doing minor changes to the docs, but probably nothing major... regards, tom lane