[cvsnt] Cleaning "fake" revisions from repository

Danail Manolov d.manolov at mail.bg
Fri Aug 5 11:12:04 BST 2005

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

Hi all

Short description of the problem:
I use latest stable of TortoiseCVS - 1.8.18 with local repository.
If I touch a file (I mean just update its date/time, but file has same
contents) and commit it, new revision is created for that file. Prior
behavior was to mark file as unmodified. Same with CVS update - prior
behavior was to mark touched file as unmodified.

I found the source of the problem, and it is in CVSNT v2.0.62.1817 that
comes with TortoiseCVS. I go to command line and execute "cvs update"
with cvsnt.exe that comes with tortoisecvs, and I have described
behavior. If I execute same command with original cvs.exe, v1.11, it
behaves like CVSNT before -  marks  file as unmodified and does not
creates new revision. This is IMHO more correct, since file contents  is
actually the same, so there is no need for new "fake" revision.
Latest CVSNT (ver. also has correct behavior.

My question is:
1. Can somebody confirm this bug in prior CVSNT version?
2. Is there a way for me to clean my repository from those "fake" 
revisions that just add noise and no useful version information?

Thanks in advance,

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook