Some svn numbers

[Marcin Dalecki]

On 2005-10-13, at 03:26, Mike Stump wrote:

> On Oct 12, 2005, at 5:55 PM, Marcin Dalecki wrote:
>
>> On 2005-10-12, at 04:42, Daniel Berlin wrote:
>>
>>> Checkouts will be about 30% slower with svn, just because it has to
>>> write more data out to disk because of the working copy
>>>
>>
>> Yes. Indeed. One suggestions comes immediately to my mind. Why  
>> don't you provide some kind of COW (Copy on Write)? Or maybe one  
>> should call it - checkout a copy on demand?
>>
>
> How does one portably do this?  How does one non-portably do  
> this?  :-)

Hmm.... thinking about it. Requiring a bit of self consciousness on  
behalf of the user I would propose
the following:

- One does a "special mode checkout". Like for example:

$ svn checkout -cow svn:/..........

- Invoking an editor involves using svn as a front-end:

$ svn edit gvim -f tralala.c

svn edit does preserve then the whole preservation of the original  
and pays attention to the result of the editing operation. This would  
be quite portable I think... The only incovenience this introduces is  
the requirement to call the editor with the character sequence "svn  
edit " as a prefix.

> ( Yes, I know, unionfs and the like, but across a reboot it dies. )

I'm too not a fan of some unreplicable-admins-best-trick solution of  
this sort.

> In emacs, you set version control, and then just use *.~1~, side  
> benefit:

Emacs: Well I'm just wondering why there still isn't any direct svn  
protocol implementation written in lisp for it :-) Maybe it got a bit  
out of fashion... After al svk is perl at it's "best".