[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: Greg Stein <gstein_at_lyra.org>
Date: 2002-08-02 03:00:22 CEST

On Thu, Aug 01, 2002 at 05:37:25PM -0700, Brian Behlendorf wrote:
> On Thu, 1 Aug 2002, Peter Davis wrote:
> > On Thursday 01 August 2002 14:44, you wrote:
> > > I'm not a fan of creating a new revision simply
> > > because somebody took out a lock on something they *might* change (they
> > > could revert and cancel their lock).
> >
> > You're right -- as soon as I started thinking about how to do this, that
> > popped out like a sore thumb. At least it would force people to submit a log
> > message saying why they took out the lock. But yes, that would pollute the
> > repository far too much.
> I dunno. Greg's proposal requires you to be running your svn repos behind
> a web server;

Not at all. The *lock mgmt* needs to run via a web server. You could still
commit locally, while your locks are being managed via your client tool and
the commit hooks.

But if you stop and think about it: it doesn't *have* to go via a web
server. I just proposed the client tool talk to the server via HTTP. If the
client tool talks to a local DB of locks... fine! No problem at all.

> I don't see how one could lock it if running local.

The tool talks to the local DB of locks. The hooks check the DB just like
normal. What's the problem? :-)

> Personally I like the idea of making it a property; the only downside is
> the revision bump, and having it trigger a commit email seems like a
> positive thing.

The 'svnres lock' could also issue an email. Not a problem there. (and I
would expect it to)


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 2 02:57:34 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.