[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Tags and scalability (was Re: Enlightenment)

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2002-10-05 18:35:14 CEST

On Fri, 2002-10-04 at 20:20, Josef Wolf wrote:
> In contrast, "svn co --read-only" (or "svn co --hard-link") would
> create hard-linked files which are set read only. This would keep you
> from changing .svn/foobar files by accident. To change a specific
> file or directory, you would issue "svn edit foobar", which actually
> would do something like "rm foobar; cp .svn/foobar .; chmod +w foobar".

Except that, as we do things right now, the text-base doesn't generally
have the same contents as the working copy file, even when there are no
local modifications to the working copy. The working copy file may be
newline-translated and keyword-translated, but the text base has to be a
precise copy of what's in the repository.

For read-only checkouts, there is no reason to use hard links to make a
text base; just don't have one. It can be constructed upon edit.

(Also, hard links between files in different directories don't work in
AFS, for what that's worth.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 5 18:35:53 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.