cvs commit confusing behaviour on modified files without changed content

[Olivier Berger]

Hi.

I'd like to report some kind of confusing behaviour about cvs commit,
and see what you folks think about (bug ?).

Let's say that I have a checked out file, that I edit, changing it's
content, and about which I later changed my mind, removing the changes.

The content gets back to the initial state, even if the modification
date of the file has changed.

If i issue a cvs commit command, cvs will ask for a commit log message,
displaying a pre-filled editor with the file marked as modified.

But as I save the message and exit the editor, nothing gets committed.

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) ?

-- 
Olivier BERGER                          IDEALX S.A.S.
Développeur senior                      15-17, av. de Ségur
01.44.42.00.00                          F-75007 PARIS
06.81.27.86.79                          http://IDEALX.com/