Login | Register
My pages Projects Community openCollabNet

Discussions > dev > Re: FSVS as a kind of "Archive Storage Engine"

fsvs
Discussion topic

2020-03-13: This site is going to be decommissioned and shut down very soon. Please copy and archive any data you wish to keep ASAP

Hide all messages in topic

All messages in topic

Re: FSVS as a kind of "Archive Storage Engine"

Author pmarek
Full name P.Marek
Date 2009-02-11 09:30:34 PST
Message
Attachments

FSVS as a kind of "Archive Storage Engine"

Author benjaminm
Full name Benjamin M.
Date 2009-02-10 21:33:22 PST
Message Phil,

Do you think it could be possible to add the following feature to FSVS:

I have a directory where only the more recent log files are kept (ex:
last 5).

$ ls
20090201.log
20090202.log
20090203.log
20090204.log
20090205.log

Here an example of how it could work:

$ fsvs commit-archive
N 20090201.log
N 20090202.log
N 20090203.log
N 20090204.log
N 20090205.log

$ ls
                         <--- 20090201.log was deleted...
20090202.log
20090203.log
20090204.log
20090205.log <--- 20090205.log was modified...
20090206.log <--- 20090206.log was created...

$ fsvs commit-archive
C 20090205.log
N 20090206.log

$ svn st file:///repository
     20090201.log <--- 20090201.log is still available ...
     20090202.log
     20090203.log
     20090204.log
     20090205.log
     20090206.log

So, the more recent revision would give access to the last version of
all files ever committed (if commit-archive was always used obviously)
no matter if the file was present in the working copy or not when the
more recent commit was done. "commit-archive" would in fact prevent any
file to be marked as "deleted" at the repository level.

Ben.
Messages per page: