Peter, the short answer is, "No." And I'm sure there are no shortage of
opinions about what you're trying to do from a methodology perspective, but
you'll need to seek them via the users_at_subversion.tigris.org list. This
list is about "the development of Subversion", not "how to do development
using Subversion". Thanks!
Peter Falson wrote:
> I'm guessing this has been covered to death but I didn't see this viewpoint discussed around the p4 edit methodology...
>
> In Perforce, if you do a p4 edit, other users can find out who has the file opened for edit.
>
> Is there a way to find out who has a checked out/working copy of a project?
>
> Background
> ==========
> I'm trying to set up subversion on a unix box with multiple programmers all working in the same source/run-time environment.
>
> At this point I'm thinking of having each programmer check out the programs they are working on into their home dir (compile into their own bin/lib for testing) then on checkin/commit remove the local file (rm <file>?), do an svn update on the shared (global) area to update the affected program(s) (and rebuild those programs into the global bin/lib).
>
> (feel free to comment on this methodology, it's not set in stone...yet)
>
> So what I'm looking for is a way for a user to be notified when they check out a program that someone else also has checked out as a working copy.
>
> I guess worst case scenario is I can warn the users if it's changed (committed) any time they either save or try to commit (although on the latter I'd probably utilise svn's information that a merge will be involved).
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2412737
--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2412876
Received on 2009-10-30 02:22:24 CET