Re: [OT] Conflict, an open source project

Hello Ben,

everyone's working copy, and only becomes read-write when you 'svn
> lock' it. Thus, you discover pre-existing locks *before* you even
> begin to edit the file.

'svn:needs-lock' property on a file, then it becomes read-only in

I wasn't aware of this. I know this is a question more appropriate for the
user list, but you are saying the svn server keeps track of who has locked
what?

Regarding your conflict-server idea: perforce solves the problem by
> keeping *all* working copy files as read-only. You need to 'p4 edit'
> a file to make it read-write, at which point the server then keeps
> track of exactly which files you're editing. You can ask the server
> (at any point) who is working on a file.

In a similar vein, is there demand from the user community to know when a
file is stale once the user begins to edit it? In other words, I think it
would be nice to notify a dev if they are not working with the latest
revision. Currently Conflict does not do this, but is in a realistic
position to do

A number of people have requested a similar mode of operation for
> subversion, since it would solve the same problem your conflict-server
> does.

I'll go off and make this happen. I'll post back here with the results as
long as your team does not mind the noise. Thanks.

---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>

-- 
Dennis Byrne