Ben Collins-Sussman wrote:
> 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.
Have we decided that this is something we really want? It does sound very
annoying and restrictive.
With the speed of the new working coy code, shouldn't we wait to see how fast
that is before even introducing 'svn edit'?
Are there any other open-source version control systems that use the read-only
model? Isn't the reason 'p4 edit' is needed is to indicate to the server the
intentions to edit the file, which svn doesn't need?
Blair
---------------------------------------------------------------------
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 01:51:25 CEST