[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: Josef Wolf <jw_at_raven.inka.de>
Date: 2002-10-05 02:20:24 CEST

On Fri, Sep 27, 2002 at 03:34:37PM -0500, Kirby C. Bohling wrote:

> With hardlinks, and checksum verifications you should be really safe to
> have the text bases in .svn be duplicated space wise if and only if
> you've changed the file.
>
> Your editor must respect hardlinks, which I believe emacs does

Emacs does this if you configure it this way. I teached my emacs
_not_ to do this. BTW: I don't like to rely on the tools (editor is
just _one_ tool!) for doing the right thing.

But maybe we could find a compromise anyway. What about the following
proposal:

"svn co" behaves as it always has. So people do not need to change
their habits as long as they have plenty of disk space.

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".

IMHO, this would give us best of both worlds:
- People with plenty of disk would never mind. The default would
  behave as it ever has.
- People who care about disk would "svn co --read-only" and
  "svn edit foobar" (they are already used to "xyz edit foobar" if
  they used perforce/clearcase before).

Comments?

-- 
-- Josef Wolf -- jw@raven.inka.de --
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 5 02:21:59 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.