18 Jun 19:56
[ANNOUNCE] FSVS 1.2.0 released
P.Marek <philipp <at> marek.priv.at>
2009-06-18 17:56:36 GMT
2009-06-18 17:56:36 GMT
Hello everybody! After a long time I'm happy to release a new version. The delay can be explained by it being incompatible with the older versions; this is the cause for it being labeled for the new 1.2 series, although the next big feature (mixed version working copies) is not included yet. For the impatient: see http://freshmeat.net/projects/fsvs (once it's updated) and http://doc.fsvs-software.org/, but don't complain afterwards(Continue reading)About the incompatibilities ============================= WAA_CHARS ----------- FSVS uses (the MD5 of) the absolute pathname as a key for storing internal data - user-defined properties, a list of block-MD5s for faster change detection, and things like that. Now that has a problem if you're (very) unlucky and two of your paths hash to the same MD5; or if you have nested working copies, eg. "/" and "/etc". Here all files in the "/etc" working copy get the same internal key as the ones below "etc" in the "/" working copy, and this will cause problems, as the FSVS-managed meta-data gets partly changed from two working copies simultaneously.
About the incompatibilities
=============================
WAA_CHARS
-----------
FSVS uses (the MD5 of) the absolute pathname as a key for storing internal
data - user-defined properties, a list of block-MD5s for faster change
detection, and things like that.
Now that has a problem if you're (very) unlucky and two of your paths hash
to the same MD5; or if you have nested working copies, eg. "/" and "/etc".
Here all files in the "/etc" working copy get the same internal key as the
ones below "etc" in the "/" working copy, and this will cause problems, as
the FSVS-managed meta-data gets partly changed from two working copies
simultaneously.
RSS Feed