Re: text-base penalty: A proposed solution

On 19 Dec 2002, Bob Gustafson <bobgus@rcnChicago.com> wrote:
> OK, how is this for a scheme to save on text-base storage:
>
> When the project is first checked out from the repository, all of the files
> are set as read-only.
>
> Suppose now that you want to edit a file. Using your favorite editor, you
> make a few changes and then go to save it. Since it is a read-only file,
> the editor complains.
>
> You execute a shell command then - an svn_init command (to be written)
> which is pretty simple, it copies the read-only file from the working space
> to the .svn text-base area and then changes the read-only to a read-write.
>
> After this command executes, you go back to the editor and redo the save.
> The situation is then exactly the same as it is now with regard to that
> single file.

Yes, I suppose that would work. However, that enormously changes the
design from CVS's "edit anything" to SCCS's/BitKeeper's/ClearCase's
"checkout, then edit." Since Svn is meant to be a CVS replacement I
think that means the architects will not be able to consider this
change.

If you were desparate for space, you could hack this up by linking the
wc to the text-base and making both readonly.

-- 
Martin 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org