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

Re: how to keep track of svn checkouts by the users

From: John Peacock <john.peacock_at_havurah-software.org>
Date: Fri, 12 Sep 2008 07:41:45 -0400

Please don't use svn_at_subversion.tigris.org as a list address; that is strictly
used for commit messages from the project itself, not for questions.

abhijit vaidya wrote:
> 1) How to know how many users checking out the respositories?
> 2) How to know about all the checkouted repositories are committed
> completely or no?

Subversion is a client/server application. There is no tight connection between
the server and the client, but only between the client and the server. By this
I mean that there is no way from the server to "ask" the client if its working
copies are up to date. When clients check out any portion of the repository,
that working copy is the only evidence that this has happened. And indeed, the
end user could just as easily check out some part of the repo and then
immediately delete the working copy and the server will have no way of "knowing"
that.

You might be able to glean some statistical information from the Apache logs (if
you are running Apache) about the number of unique client interactions over any
given time span. But that is about it; you won't even be able to get any useful
data about what paths were checked out (since that information is part of the
DAV communication that is not logged).

It sounds like you want to have something like Perforce, where each client has
to register with the server what it is checking out.

Sorry

John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-12 13:42:08 CEST

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.