[Discuss] Versioning File Systems

[j.natowitz at rcn.com (Jerry Natowitz)]

You took my comment out of context:
>On 05/05/2012 03:13 PM, MBR wrote:
>In the context of software development, it is much more important to
>have a snapshot of ALL FILES at any point in time than one particular
>file, since they depend on each other so heavily.  Versioning
>filesystems won't do that. 

I was responding to MBR.
Versioning filesystems are not designed to allow you to see the state of the filesystem at any arbitrary point in the past.  Aside from any other issues, I do not believe they have the ability to remove a file from the "current view", but leave all the generations of that file available for constructing a "veiw in the past".

---- Original message ----
>Date: Mon, 07 May 2012 11:13:25 -0400
>From: discuss-bounces+j.natowitz=rcn.com at blu.org (on behalf of Richard Pieri <richard.pieri at gmail.com>)
>Subject: Re: [Discuss] Versioning File Systems  
>To: discuss at blu.org
>
>On 5/7/2012 8:22 AM, Jerry Natowitz wrote:
>> So in essence, you want a filesystem that does the equivalent of
>> taking a snapshot every time the filesystem changes.
>
>No.  Saving or modifying a file on a versioning file system is 
>equivalent to "RENAME FILE.TXT FILE.TXT;23", where "23" is the next 
>available version number, and writing out a new FILE.TXT.  There is an 
>optional step of removing old versions if there is a set limit to the 
>number of concurrent versions allowed.
>
>It's really that simple.
>
>-- 
>Rich P.
>_______________________________________________
>Discuss mailing list
>Discuss at blu.org
>http://lists.blu.org/mailman/listinfo/discuss