I have no thread handy, but it's been discussed over and over in the
wc-ng design as an 'eventual feature' to be implemented. It's
basically imitating perforce: the entire working copy is read-only.
When you want to edit a file, you run 'svn edit file', which makes the
file read-write and registers this fact in sqlite. Then, when you run
'svn status', 'svn diff', 'svn commit', etc. there's no need to crawl
the tree trying to discover local edits; you just ask the database
which files to stat. It makes things shockingly fast, and while it
sounds horribly annoying and restrictive to a veteran CVS or SVN user,
it's actually a really nice way to work.
On Fri, Oct 24, 2008 at 4:28 PM, Neels J Hofmeyr <neels_at_elego.de> wrote:
>
>
> Ben Collins-Sussman wrote:
>> Or, just wait for the working-copy rewrite (in progress now) to
>> implement an 'svn edit' command. No more crawling the working copy at
>> all.
>
> Say, what?
> Got a pointer for me that explains it?
>
> Thanks
> ~Neels
>
> --
> Neels Hofmeyr -- elego Software Solutions GmbH
> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> phone: +49 30 23458696 mobile: +49 177 2345869 fax: +49 30 23458695
> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
> Handelsreg: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-25 00:16:35 CEST