Re: automating cvs checkout/checkin and also don't checkin

[Larry Jones]

Eric Siegerman writes:
> 
> If you're working client/server, CVS will tell you in its
> log-message-editor comments that the file is "modified", but it
> won't actually check in a new revision.  That little mislead
> happens because at the time CVS collects the log message, it
> knows which files have different timestamps, but doesn't yet know
> which subset of them also have different content.  (It can't diff
> the files until it's sent the sandbox copy to the server (duh),
> and it can't do that until it has the log message, because it
> needs to send all data necessary for the commit to the server in
> one go, without any pauses for user interaction.)

However, if you do an update before you commit (which you should, to
check for other changes that might conflict with your changes), *that*
will send all the files with different timestamps to the server and
determine which have really been modified, eliminating the "false
positives" in the log message editor.

-Larry Jones

I'm crying because out there he's gone, but he's not gone inside me. -- Calvin