On Sep 12, 2008, at 06:41, John Peacock wrote:
> 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).
You can write a post-checkout hook to do whatever you want when
someone checks out from your repository. That's going to be the
extent of what you can do, though. As John said, the server cannot
know whether users have uncommitted changes in working copies.
Subversion does not have a post-checkout hook, but you can fake it
using my svnhookdispatcher script, provided you're serving your
repository using Apache and not svnserve:
http://www.ryandesign.com/svnhookdispatcher/
---------------------------------------------------------------------
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-13 00:56:06 CEST