"Bruce Momjian" <[EMAIL PROTECTED]> writes:
> (Who says were obsessive?) :-)
I may not fall into your clever trap...
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1:
Personally I find CVS so terribly slow for large trees like Postgres that it's
essential to use rsync to maintain a local CVS repository. That makes 'cvs
diff' remarkably fast.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
ed to
using rsync. The alternative is to manually edit the Entries files to list the
new files.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Those lines go to stderr. If you do "cvs diff > file" it spits out all the cvs
file statuses to the terminal but dumps the diff to the file.
It doesn't matter, diffs can contain arbitrary junk between the file diffs.
patch only looks at the things it recognizes.
--
Gregory S
