Michael Gersten wrote:
> 
> Or hitting space to wake the machine, and then hitting
> backspace because it went into the editor (instead of hitting
> undo).

Or running a sed script over every file.  Most of them will not
be changed.  Or applying a patch, which fails, so you back it
out again.

> All I know is that 'cvs -n update' shows no changes, but takes
> a long time (as it compares files); 'cvs update' takes a long
> time the first time, to make it think 'no changes'.

Try cvs -t update.  You'll be able to see the client sending
the files back to the server, before the client ever prints anything.

What scares me more is doing a cvs ci and EVERY file is shown
in the commented-out bit of the log message template.  cvs up
gets things sane again, but it never fails to give me a fright.

Regards,

Mitch.
--
| mailto:[EMAIL PROTECTED]       | Not the official view of: |
| mailto:[EMAIL PROTECTED] | Australian Calculator Opn |
| Certified Linux Evangelist! | Hewlett Packard Australia |

Reply via email to