You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Daragh Fitzpatrick <Da...@UChicago.edu> on 2004/07/07 21:56:29 UTC

'checkout' state

Hi,

	I know it's not what SVN does, but is it possible to know if another
user is working on a file? The merging concept does not work so well for
binary files such as word documents. Is any tool available to allow users to
set such a flag? (reminds me of the conch from the Lord of the Flies)

Cheers,

          :D

--------------------------------------------------------------------
Daragh Fitzpatrick        Daragh@UChicago.edu         (773) 702-8976

Solutions Architect                      NSIT Administrative Systems
Renewal Projects and Architecture              University of Chicago
--------------------------------------------------------------------


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

Re: 'checkout' state

Posted by Max Bowsher <ma...@ukf.net>.
Daragh Fitzpatrick wrote:
> If I understand you correctly, this would prevent a user from committing
> while another user has the file 'out', but wouldn't let the user know that
> another has the file before they started working on it. I.e., after the
> fact. Is there a checkout event?

Well, I assume that before someone began work, they would lock the file.

I imagine you would need a script to avoid the locking being tedious, so
that script could check for an existing lock property.

It's not a perfect solution, but if you really need locking *now* and are
already using subversion, a set of scripts like I've hypothesized is a
possible solution.


Max.


>
> Cheers,
>
>           :D
>
> --------------------------------------------------------------------
> Daragh Fitzpatrick        Daragh@UChicago.edu         (773) 702-8976
>
> Solutions Architect                      NSIT Administrative Systems
> Renewal Projects and Architecture              University of Chicago
> --------------------------------------------------------------------
>
> -----Original Message-----
> From: Max Bowsher [mailto:maxb@ukf.net]
> Sent: Wednesday, July 07, 2004 5:26 PM
> To: Daragh@uchicago.edu; users@subversion.tigris.org
> Subject: Re: 'checkout' state
>
> Daragh Fitzpatrick wrote:
>> Hi,
>>
>> I know it's not what SVN does, but is it possible to know if another
>> user is working on a file? The merging concept does not work so well
>> for binary files such as word documents. Is any tool available to
>> allow users to set such a flag? (reminds me of the conch from the Lord
>> of the Flies)
>
> Well, if you don't mind lock/unlock events showing up as commits, you can
> whip up a simple locking system using scripts.
>
> Just set a property to your username to lock a file, and have a pre-commit
> script that aborts commits that attempt to change a file with the lock
> property set and not equal to the username of the user doing the commit.
>
> Max.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org


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

RE: 'checkout' state

Posted by Daragh Fitzpatrick <Da...@UChicago.edu>.
If I understand you correctly, this would prevent a user from committing
while another user has the file 'out', but wouldn't let the user know that
another has the file before they started working on it. I.e., after the
fact. Is there a checkout event?

Cheers,

          :D

--------------------------------------------------------------------
Daragh Fitzpatrick        Daragh@UChicago.edu         (773) 702-8976

Solutions Architect                      NSIT Administrative Systems
Renewal Projects and Architecture              University of Chicago
--------------------------------------------------------------------

-----Original Message-----
From: Max Bowsher [mailto:maxb@ukf.net] 
Sent: Wednesday, July 07, 2004 5:26 PM
To: Daragh@uchicago.edu; users@subversion.tigris.org
Subject: Re: 'checkout' state

Daragh Fitzpatrick wrote:
> Hi,
>
> I know it's not what SVN does, but is it possible to know if another 
> user is working on a file? The merging concept does not work so well 
> for binary files such as word documents. Is any tool available to 
> allow users to set such a flag? (reminds me of the conch from the Lord 
> of the Flies)

Well, if you don't mind lock/unlock events showing up as commits, you can
whip up a simple locking system using scripts.

Just set a property to your username to lock a file, and have a pre-commit
script that aborts commits that attempt to change a file with the lock
property set and not equal to the username of the user doing the commit.

Max.


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


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

Re: 'checkout' state

Posted by Max Bowsher <ma...@ukf.net>.
Daragh Fitzpatrick wrote:
> Hi,
>
> I know it's not what SVN does, but is it possible to know if another
> user is working on a file? The merging concept does not work so well for
> binary files such as word documents. Is any tool available to allow users to
> set such a flag? (reminds me of the conch from the Lord of the Flies)

Well, if you don't mind lock/unlock events showing up as commits, you can whip up a simple locking system using scripts.

Just set a property to your username to lock a file, and have a pre-commit script that aborts commits that attempt to change a file
with the lock property set and not equal to the username of the user doing the commit.

Max.


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