On Thu, Jun 13, 2013 at 4:24 PM, Benjamin Fritz wrote:
> On Thu, Jun 13, 2013 at 3:09 PM, Mark Phippard wrote:
>> On Thu, Jun 13, 2013 at 4:05 PM, Benjamin Fritz
>> wrote:
>>> On Thu, Jun 13, 2013 at 2:47 PM, Mark Phippard wrote:
The hook is running on the server, so it could access
On Thu, Jun 13, 2013 at 3:09 PM, Mark Phippard wrote:
> On Thu, Jun 13, 2013 at 4:05 PM, Benjamin Fritz
> wrote:
>> On Thu, Jun 13, 2013 at 2:47 PM, Mark Phippard wrote:
>>>
>>> The hook is running on the server, so it could access the repository
>>> via file:// URL to do the lock. This does n
On Thu, Jun 13, 2013 at 4:05 PM, Benjamin Fritz wrote:
> On Thu, Jun 13, 2013 at 2:47 PM, Mark Phippard wrote:
>>
>> The hook is running on the server, so it could access the repository
>> via file:// URL to do the lock. This does not require authentication.
>>
>
> I DID NOT KNOW THIS! Is that d
On Thu, Jun 13, 2013 at 2:47 PM, Mark Phippard wrote:
>
> The hook is running on the server, so it could access the repository
> via file:// URL to do the lock. This does not require authentication.
>
I DID NOT KNOW THIS! Is that documented somewhere? This should allow
my pre-lock hook to work e
On Thu, Jun 13, 2013 at 3:41 PM, Benjamin Fritz wrote:
> Where I work, we branch for every bugfix, to allow a "clean" trunk at all
> times.
>
> Some files we work with are not easily merged, so we have
> svn:needs-lock set on them.
>
> Locking one of these files is supposed to indicate to the res
