Re: linux-2.5.4-pre1 - bitkeeper testing

[Hans Reiser <reiser@namesys.com>]

Rik van Riel wrote:

>On Sun, 10 Mar 2002, Alan Cox wrote:
>
>>>It was fabulous at that time. The first time you create a file, it gets ";1"
>>>appended to it's filename. When you edit it, it gets saved under the same name,
>>>this time appended by ";2". Edit it again... whell, you get the picture.
>>>Cleaning up was as simple as "$ PURGE /KEEP=3" to keep the last three versions.
>>>
>>>For these days with sometimes hundreds of files, it might become confusing when
>>>'ls' shows all versions of all files, but back then it worked well.
>>>
>>Its trickier than that - because all your other semantics have to align,
>>its akin to the undelete problem (in fact its identical). Do you version
>>on a rewrite, on a truncate, only on an O_CREAT ?
>>
>
>That's a nice question.  I would dread the scenario where a
>new version was created for each append ;))
>
>Rik
>
I think that file close is the right place for it.

Again, only for those files/plugins that have VERSION_ON_FILE_CLOSE 
enabled.....

With regard to unlink, I think I don't see the problem.  Unlink makes 
the default version non-existent.

You need a default version, something like filenameA/..default with 
filename A resolving to filenameA/..default.  Listing the default 
version of a directory only lists the current default versions of files.

Hans