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

Re: Notification of checkouts (was: Re: Finding Locks)

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-09-20 19:49:48 CEST

On Sep 17, 2007, at 10:19, Bicking, David (HHoldings, IT) wrote:

> I was interrupted from writing this just now by someone arguing
> vigorously for the importance of the user being notified when someone
> else has any file "checked out" (I'm not even talking about locks
> here).
> Perhaps it is just a philosophical difference that cannot be bridged
> with some people.

Note that the Subversion operation "checkout" does not really
correspond with a dictionary definition of "check out". If you think
of "check out" as in a public library, when you check out a book, you
physically take the book away, and nobody else can have it until you
check it back in. But in Subversion, "checkout" really means "get a
copy". It would be like going to the library and photocopying
whatever material you want and taking the photocopies home. Anybody
else can still go to the library and do the same. And just because
you took home some photocopies, that doesn't mean you'll ever bring
them back with notes in the margins expecting them to be incorporated
into the original book. You might do that (svn commit workingcopy),
or you might just as easily throw the photocopies away after you've
looked at them (rm -rf workingcopy). Given this, it's not necessarily
useful to know when someone checks out the code.

If you still want to be notified when someone "gets a copy",
Subversion does not provide hooks for this, but you can fake them, as
long as you are serving your repository using Apache 2. I provide a
script that helps you with this:


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 20 19:51:52 2007

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.