Thanks Philip for sharing your insight into the lock mechanisms.
Sorry about the delay, wanted to find time to investigate.
On 24 feb 2014, at 19:56, Philip Martin wrote:
> Thomas Åkesson writes:
>
>> Svn does not allow locking non-existent paths. It is blocked both in
>> libsvn_fs_base/libs
Hi,
Von: Ben Reser [mailto:b...@reser.org]
> On 2/24/14, 8:30 AM, Thomas Åkesson wrote:
> > We would like to enhance the locking in Subversion to support use cases
> where the user needs to ensure that added files will be possible to commit.
> There are a couple of use cases:
> >
> > 1. Adding fil
> On 24 feb 2014, at 20:36, Ben Reser wrote:
>
>> On 2/24/14, 8:30 AM, Thomas Åkesson wrote:
>> We would like to enhance the locking in Subversion to support use cases
>> where the user needs to ensure that added files will be possible to commit.
>> There are a couple of use cases:
>>
>> 1. A
Philip Martin writes:
> Ben Reser writes:
>
>> On 2/24/14, 11:10 AM, Philip Martin wrote:
>>> It's hard to fix. Commit and unlock are separate filesystem operations
>>> and the server can always die, or fail the unlock, after the commit. I
>>> suppose a new filesystem might have a commit-and-un
Ben Reser writes:
> On 2/24/14, 11:10 AM, Philip Martin wrote:
>> It's hard to fix. Commit and unlock are separate filesystem operations
>> and the server can always die, or fail the unlock, after the commit. I
>> suppose a new filesystem might have a commit-and-unlock operation but
>> how could
On 2/24/14, 11:10 AM, Philip Martin wrote:
> It's hard to fix. Commit and unlock are separate filesystem operations
> and the server can always die, or fail the unlock, after the commit. I
> suppose a new filesystem might have a commit-and-unlock operation but
> how could FSFS solve it? We might
On 2/24/14, 8:30 AM, Thomas Åkesson wrote:
> We would like to enhance the locking in Subversion to support use cases where
> the user needs to ensure that added files will be possible to commit. There
> are a couple of use cases:
>
> 1. Adding files that are dependencies to other files, where th
"C. Michael Pilato" writes:
> On 02/24/2014 01:56 PM, Philip Martin wrote:
>> There is a way to create such locks at present: checkout, lock a
>> file, delete the file or parent directory, commit with --no-unlock.
>> We have a regression test for this:
>> lock_tests.py:deleted_path_lock. (Possibl
On 02/24/2014 01:56 PM, Philip Martin wrote:
> Thomas Åkesson writes:
>
>> Svn does not allow locking non-existent paths. It is blocked both in
>> libsvn_fs_base/libsvn_fs_fs as well as in mod_dav_svn. In the same
>> areas of the code in fs comments say:
>> "While our locking implementation easily
Thomas Åkesson writes:
> Svn does not allow locking non-existent paths. It is blocked both in
> libsvn_fs_base/libsvn_fs_fs as well as in mod_dav_svn. In the same
> areas of the code in fs comments say:
> "While our locking implementation easily supports the locking of
> nonexistent paths, we del
Hi,
We would like to enhance the locking in Subversion to support use cases where
the user needs to ensure that added files will be possible to commit. There are
a couple of use cases:
1. Adding files that are dependencies to other files, where the reference
mechanism is cumbersome. Simple case
11 matches
Mail list logo
