> > How would you suggest I invoke the patch utility to get this to
> > work?
> 1. save patch file to doc/src/sgml/history.sgml.patch
> 2. cd doc/src/sgml
> 3. patch < history.sgml.patch
Hmm. Somehow since it had the doc/src/sgml path in the names I put it
up in the top level directory, but it wasn't happy. Didn't try exactly
what you suggest. btw, I'm running the same version of patch as
yourself.
> The one thing about renaming the original files to .orig is that I get
> confused when doing cvs updates. By keeping all of my changes in .new
> files, it's clearer to me which of my changes made it into the
> official Postgres repository. But again, I'll do whatever makes it
> easier for you.
Well, easiest for me is probably filename.sgml.orig and filename.sgml,
just because that is the form for all of the other patches we get.
btw, you might want to use cvsup to pull over the CVS repository.
Then, you can easily diff and update your local working tree via local
cvs without the risk of blowing away any changes you might have made.
And cvs will show you which files have changed, even if you forget to
rename them or save a .orig version. The newest version of the docs
have an appendix on cvs/cvsup access.
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
