On Thu, Aug 23, 2012 at 12:26 AM, Philip Martin
wrote:
> Johan Corveleyn writes:
>
>> Ok, let me try to decipher what that means for users.
>>
>> - New commit will block: does this mean that 'svn commit -mm somefile'
>> will simply hang (until the repository is unfrozen, or until the
>> client-si
Johan Corveleyn writes:
> Ok, let me try to decipher what that means for users.
>
> - New commit will block: does this mean that 'svn commit -mm somefile'
> will simply hang (until the repository is unfrozen, or until the
> client-side timeout is reached)? Can it be cancelled?
>
> - Commit in pro
> -Original Message-
> From: pbu...@apache.org [mailto:pbu...@apache.org]
> Sent: woensdag 22 augustus 2012 19:41
> To: comm...@subversion.apache.org
> Subject: svn commit: r1376154 - in /subversion/branches/inheritable-
> props/subversion: libsvn_wc/upgrade.c libsvn_wc/wc-metadata.sql
>
On Wed, Aug 22, 2012 at 9:39 PM, Philip Martin
wrote:
> Johan Corveleyn writes:
>
>> On Fri, Aug 10, 2012 at 10:22 AM, Philip Martin
>> wrote:
>>> Johan Corveleyn writes:
>>>
So, say for a standard 1.8 FSFS repository, is there a timeout for
commits? What's the timeout (is it configur
On 22.08.2012 21:29, Johan Corveleyn wrote:
> On Wed, Aug 22, 2012 at 6:28 PM, C. Michael Pilato
> wrote:
> ...
>> * besides, philip's freeze/unfreeze offers a far more logical way to
>> get honest-to-goodness-read-only-ness.
> Like I asked in the thread about the freeze/unfreeze feature: what
Johan Corveleyn writes:
> On Fri, Aug 10, 2012 at 10:22 AM, Philip Martin
> wrote:
>> Johan Corveleyn writes:
>>
>>> So, say for a standard 1.8 FSFS repository, is there a timeout for
>>> commits? What's the timeout (is it configurable?)? How will the commit
>>> fail when it reaches the timeout
On Wed, Aug 22, 2012 at 6:28 PM, C. Michael Pilato wrote:
...
> * besides, philip's freeze/unfreeze offers a far more logical way to
> get honest-to-goodness-read-only-ness.
Like I asked in the thread about the freeze/unfreeze feature: what
happens to a client committing to a frozen repository?
On Fri, Aug 10, 2012 at 10:22 AM, Philip Martin
wrote:
> Johan Corveleyn writes:
>
>> So, say for a standard 1.8 FSFS repository, is there a timeout for
>> commits? What's the timeout (is it configurable?)? How will the commit
>> fail when it reaches the timeout?
>
> I don't think there is a time
On 08/22/2012 02:02 PM, Branko Čibej wrote:
> On 22.08.2012 18:28, C. Michael Pilato wrote:
>> * besides, philip's freeze/unfreeze offers a far more logical way to
>> get honest-to-goodness-read-only-ness.
>
> The only caveat here being that using repo freeze could not be used
> instead of start
On 22.08.2012 18:28, C. Michael Pilato wrote:
> * besides, philip's freeze/unfreeze offers a far more logical way to
> get honest-to-goodness-read-only-ness.
The only caveat here being that using repo freeze could not be used
instead of start-commit blocking commits whilst importing code from a
On Wed, Aug 22, 2012 at 12:28 PM, C. Michael Pilato wrote:
> Bert asked the question of what would trigger the new start-commit behavior
> -- upgrade to 1.8? A format bump for the repository? Personally, I lean
> towards just the 1.8 upgrade. I don't feel like this only justifies a
> format bu
After IRC conversation between myself, brane, markphip, stsp, danielsh, and
(to a less degree) julianf, I think I have a clear path forward on this now.
The general sentiments are:
* that 'start-commit' is today useful for making a repository "truly
read-only" (as in, not modifiable at all) is
Daniel Shahaf writes:
> Philip Martin wrote on Tue, Aug 21, 2012 at 20:42:55 +0100:
>> Daniel Shahaf writes:
>>
>> > Philip Martin wrote on Tue, Aug 21, 2012 at 18:00:23 +0100:
>> >> Functions like fs_library_vtable_t.pack_fs and
>> >> fs_library_vtable_t.recover that don't take the common_pool
13 matches
Mail list logo