On Montag, 2. Juli 2007 Thomas Harold wrote:
> I've seen a situation with 1.1.5 where "fsvs ci" from the root (which is
> also the WC root) checks in items that don't show up on the "fsvs
> status" list. So I need to sit down and examine my ignore list in
> greater detail later this week and see if I can make it happen
> repeatedly.  I've seen it happen twice now, but have yet to go digging.

A "fsvs status" looks at the sizes and timestamps.
If the size is different, the file is known to be changed; if only the ctime 
or mtime differs, it *may* have changed.
For directories the size does not really help much.

The difference between "commit" and "status" is that "status" is faster, ie. 
it doesn't always check if there are *really* changes.
If you need an exact result, you can do
        fsvs status -C
which checks directories for new entries even if their timestamps haven't 
changed, or 
        fsvs status -C -C
which does an additional MD5 check over files.


Commit does include a single "-C", so it *may* find changes that status 
doesn't show.

1.1.7 will allow to define the checksum level in the configuration file.


Regards,

Phil


-- 
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to