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

Re: [Issue 533] New - implement reserved checkouts

From: Dave Cridland <dave_at_cridland.net>
Date: 2002-08-14 23:13:43 CEST

On Tue, 2002-08-13 at 20:38, Greg Hudson wrote:
> On Tue, 2002-08-13 at 12:53, Jim Blandy wrote:
> > =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@xbc.nu> writes:
> > > 2. It must be possible to lock non-HEAD revisions, so that branches
> > > can't be made from them.
> >
> > Why is this important?
> I'll go farther: is it desirable that you can't make a copy of a locked
> revision? It seems like if someone has locked a file you want to edit,
> one of the possible recourses is to make a copy of it and edit that
> instead. (Copies == branches for us, of course.)

Which, IIRC, you can do with a typical Office file in Windows.

Not saying this makes it *right*, but at least it would seem consistent
with the most prevalent instance of locking from a user's perspective.

I seems "right" to me, as well.

As for VSS, I recall that you can "copy" a locked file, but:

a) In VSS, it's the equivalent of a "ln" anyway, rather than a "cp".
b) The "new" file, being linked, remains locked.

What I can't recall is whether a link can be broken (so it becomes an
SVN copy/branch) when it's locked. I suspect not.

Perhaps it's a repository (or file, or both) configurable thing?

Do we have repository settings? If not, I suppose we could invent a new
node type and have them as properties on it. Maybe. Bit of a hack, I


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 14 23:09:41 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.