Justin, you appear to have resurfaced (to a degree, at least). Did you ever
complete this work?
On 06/18/2012 02:18 AM, Justin Erenkrantz wrote:
> One issue that I've come across in my recent analysis is that ra_serf
> isn't always aggressive in closing directories when doing an update.
> Specifi
On 10.08.2012 01:15, Philip Martin wrote:
> Philip Martin writes:
>
>> Yes, I think so. The process executes something like
>>
>>pragma locking_mode = exclusive;
>>begin exclusive transaction;
>>commit transaction;
>>
>> and then the lock persists until the database connection is clos
On Wed, Aug 8, 2012 at 1:40 PM, Philip Martin
wrote:
> Subversion 1.7.6 tarballs are now available for testing/signing by
> committers. To obtain them please check out a working copy from
> https://dist.apache.org/repos/dist/dev/subversion
+1 for release.
Tested on Mac OS X 10.7.4.
All tests pa
Mark Phippard writes:
> Does our write lock block svn lock/unlock as well as revprop edits?
Yes, for FSFS. I haven't investigated a BDB implementation of freeze.
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download
On Aug 9, 2012, at 7:15 PM, Philip Martin wrote:
> Philip Martin writes:
>
>> Yes, I think so. The process executes something like
>>
>> pragma locking_mode = exclusive;
>> begin exclusive transaction;
>> commit transaction;
>>
>> and then the lock persists until the database connectio
Philip Martin writes:
> Yes, I think so. The process executes something like
>
>pragma locking_mode = exclusive;
>begin exclusive transaction;
>commit transaction;
>
> and then the lock persists until the database connection is closed or
> the process exits.
I think it might also wo
Ben Reser writes:
> On Thu, Aug 9, 2012 at 12:51 PM, Johan Corveleyn wrote:
>> On Thu, Aug 9, 2012 at 10:06 AM, Philip Martin
>> wrote:
>>> The freeze-lock is similar to a write-lock: it exists for the duration
>>> of the process that creates it. For scripts my trial freeze-program has
>>> an
Stefan Fuhrmann writes:
> On Thu, Aug 9, 2012 at 10:06 AM, Philip Martin
> wrote:
>> The freeze-lock is similar to a write-lock: it exists for the duration
>> of the process that creates it.
>
> I see. Makes sense. Will it also work for the sqlite lock?
> (you mentioned that you would like to lo
On Thu, Aug 9, 2012 at 12:51 PM, Johan Corveleyn wrote:
> On Thu, Aug 9, 2012 at 10:06 AM, Philip Martin
> wrote:
>> The freeze-lock is similar to a write-lock: it exists for the duration
>> of the process that creates it. For scripts my trial freeze-program has
>> an interface like:
>>
>>fr
On Wed, Aug 8, 2012 at 1:40 PM, Philip Martin
wrote:
> Subversion 1.7.6 tarballs are now available for testing/signing by
> committers. To obtain them please check out a working copy from
> https://dist.apache.org/repos/dist/dev/subversion
>
> Please add your signatures to the .asc files there.
>
On Thu, Aug 9, 2012 at 10:06 AM, Philip Martin
wrote:
> Stefan Fuhrmann writes:
>
>> On Wed, Aug 8, 2012 at 4:57 PM, Mark Moe wrote:
>>> This would be useful for our us too. I would add "freeze" to the start and
>>> "unfreeze" to the end of the script we use to rsync a copy of our repo (and
>>>
On 08.08.2012 18:14, Bert Huijben wrote:
> Windows 5.0, 5.1 and 5.2 (2000, XP and 2003) are still in use and are
> now identified as vista, 7 and 8 and the next version might just be
> 7.0, so I would recommend checking the major version before attaching
> names.
(Lost this amongst commit messages
On Thu, Aug 9, 2012 at 10:06 AM, Philip Martin
wrote:
> Stefan Fuhrmann writes:
>
>> On Wed, Aug 8, 2012 at 4:57 PM, Mark Moe wrote:
>>> This would be useful for our us too. I would add "freeze" to the start and
>>> "unfreeze" to the end of the script we use to rsync a copy of our repo (and
>>>
On 08/08/2012 01:40 PM, Philip Martin wrote:
> Subversion 1.7.6 tarballs are now available for testing/signing by
> committers. To obtain them please check out a working copy from
> https://dist.apache.org/repos/dist/dev/subversion
Summary:
+1 to release.
Platform:
Ubuntu 10.04.4 (lucid)
On 08/09/2012 12:08 PM, C. Michael Pilato wrote:
> On 08/08/2012 01:40 PM, Philip Martin wrote:
>> Subversion 1.7.6 tarballs are now available for testing/signing by
>> committers. To obtain them please check out a working copy from
>> https://dist.apache.org/repos/dist/dev/subversion
>>
>> Please
On 08/08/2012 01:40 PM, Philip Martin wrote:
> Subversion 1.7.6 tarballs are now available for testing/signing by
> committers. To obtain them please check out a working copy from
> https://dist.apache.org/repos/dist/dev/subversion
>
> Please add your signatures to the .asc files there.
> You can
Daniel Shahaf wrote on Thu, Aug 09, 2012 at 12:25:44 +0100:
> Does this property hold for f6 / 1.8?
It seems to me it would work via one of two methods,
1) rsync --delete the $rev.* files and then reconstruct the manifest on
the target;
2) exclude revprops/ from the rsync and just use 'svnsync
The question of keeping a FSFS mirror repository using rsync came up.
For FSFS f4 it's possible to do an rsync of just the rev file + revprop
file + 'current' from post-commit. (Yes, the prior revisions must be a
byte-for-byte match, and min-unpacked-rev must agree as well.
As to rep-cache.db, it
Stefan Fuhrmann writes:
> On Wed, Aug 8, 2012 at 4:57 PM, Mark Moe wrote:
>> This would be useful for our us too. I would add "freeze" to the start and
>> "unfreeze" to the end of the script we use to rsync a copy of our repo (and
>> associated files) to an off-site network share.
>
> If freeze
19 matches
Mail list logo
