Re: cvs commit confusing behaviour on modified files without changed content

[Laird Nelson]

Olivier Berger wrote:
> As cvs has connected to the server, it detects that the content hasn't
> changed, and doesn't commit anything without notifying me.
> 
> So everything looks like the commit aborted for some unreported reason.
> 
> What do you think about that  (client 1.10.7 - server 1.10.6) ?

I think you can use the cvs commit -f option, which forces the commit to
take place (perhaps put it in your .cvsrc).  :-)  Be forewarned that
sometimes this used to crash cvs 1.10; I'm not sure about 1.10.x.

Cheers,
Laird