[Cvsnt] Problem: Udate file, when file-timestamp is changed, but not the file-content

[Torsten Martinsen]

It's not a bug, it's a feature :-)

This is the reason why the TortoiseCVS client (www.tortoisecvs.org) can be configured to automatically perform a 'cvs unedit' on a file after a 'cvs commit' - if the file was changed, the 'commit' will have committed it - if it was not changed, 'unedit' will remove the edit and make the file read-only (if 'watch on' is in effect).

-Torsten

----- Original Message -----
From: <Bernhard.Berbuir at Sparkassen-Informatik.de>
To: <cvsnt at cvsnt.org>
Sent: Friday, June 07, 2002 11:51 AM
Subject: [Cvsnt] Problem: Udate file, when file-timestamp is changed, but not the file-content


>
> Hi,
> i have a problem when updating a file, which timestamp has been changed,
> but its content has not  been changed. CVS.EXE reports an returncode 0,
> but:
> * the lock (we work only with edit -c / commit -c) still exists
> * the file is marked as comittable
> * the READ-ONLY flag is absent
>
> Is this a know bug ? does anyone know this problem?

_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt