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

Re: Cross-branch locking

From: Aleksey Nogin <aleksey_at_nogin.org>
Date: 2005-09-15 12:54:49 CEST

On 15.09.2005 03:13, Ryan Schmidt wrote:

>> Actually, this is trivial in CVS - in CVS the server has a "version"
>> file for each file that is being versioned and if you create a symbolic
>> link on the server, then things just work!
>> We are in the process of migrating from CVS and it is the only feature
>> of CVS that we miss (and we miss it a lot).
> I don't think that anything that involves messing with the internal
> database structure of the repository can be considered a "feature" of
> the system.

Well, CVS does intentionally support this (as opposed to this being an
accidental consequence of the repository structure) and the CVS change
log does include entries related to making this work correctly. And mort
importantly, this is considered a reasonable think to do (as in: if I
discover a bug related to this, it will most likely be taken seriously).

> You could probably make Subversion do all sorts of
> interesting things too if you muck around with the contents of the
> files in the repository directory.

Well, if there is a way to "muck around" in subversion to allow sharing
of files between different projects in a single repository, I'd be
_very_ happy to know about it. Especially if it works reliably. And
especially if it is something that would actually be considered a
"supported" way of using subversion (as in: bugs related to such usage
will not be discared with "this is not something you should be doing").

Aleksey Nogin
Home Page: http://nogin.org/
E-Mail: nogin@cs.caltech.edu (office), aleksey@nogin.org (personal)
Office: Moore 04, tel: (626) 395-2200
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 15 12:56:43 2005

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

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