On Jan 19, 2011, at 03:32, Jan Keirse wrote:
> I'm not asking for a lock on part of the file, in fact if you think about
> it I'm not asking a real lock, i'm only asking a notification, informing
> the developer who else is working on the file.
[snip]
> I'm not asking to automatically stop th
Johan Corveleyn schreef op 19/01/2011 09:38:41:
> On Wed, Jan 19, 2011 at 9:00 AM, Jan Keirse wrote:
> > Ryan Schmidt schreef op 18/01/2011
> > 22:34:24:
> >
> >> On Jan 18, 2011, at 08:15, Jan Keirse wrote:
> >>
> >> I don't think Subversion's locking mechanism is something that can
> >> be
On Wed, Jan 19, 2011 at 9:00 AM, Jan Keirse wrote:
> Ryan Schmidt schreef op 18/01/2011
> 22:34:24:
>
>> On Jan 18, 2011, at 08:15, Jan Keirse wrote:
>>
>> > we would like to be able to always know who else is working on a file,
> so
>> > that we can communicate with each other and avoid complex
Ryan Schmidt schreef op 18/01/2011
22:34:24:
> On Jan 18, 2011, at 08:15, Jan Keirse wrote:
>
> > we would like to be able to always know who else is working on a file,
so
> > that we can communicate with each other and avoid complex merges.
> > Case 1: If 2 or 3 users have to change the sa
On Jan 18, 2011, at 08:15, Jan Keirse wrote:
> we would like to be able to always know who else is working on a file, so
> that we can communicate with each other and avoid complex merges.
> Case 1: If 2 or 3 users have to change the same file but one user has to
> make his changes in the top o
Hello,
we would like to be able to always know who else is working on a file, so
that we can communicate with each other and avoid complex merges.
Case 1: If 2 or 3 users have to change the same file but one user has to
make his changes in the top of the file, someone else is making changes to
