Re: [boost] [1.41][serialization] MSVC 9 crashes on compilation

Subject: Re: [boost] [1.41][serialization] MSVC 9 crashes on compilation
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2009-11-16 09:39:34

Beman Dawes wrote:

> On Sun, Nov 15, 2009 at 8:11 PM, Robert Ramey <ramey_at_[hidden]> wrote:
>> Note that SVN permits one to "lock" the branch for commits.  This might
>> be useful during "critical" periods to catch these kinds of errors.
> 
> As an experiment, I've locked branches/release while I build a new
> release candidate.

> One problem: It took just one minute shy of two hours to apply the
> lock. That's no fun. 

Wow. Presumably lock of entire branch is not the primary use case for 
'svn lock'. You can actually do:

        svn cp ^/branches/release ^/branches/1_41_0_final
          svn sw ^/branches/1_41_0_final

as the first step in release preparation. That's likely
to be much faster.

(The ^ syntax works only if you're in a working copy). 

> Presumably it will take another two hours to
> unlock it. As an aside, I wonder how long the equivalent operation
> would have taken with Git?

Well, given that git does not have locks, it's a trick question. You
can write a hook to disable commits to a specific branch, and install
that hook in no time -- but you can do the same in subversion (or use
path-based authorization). In both cases, you need direct access to server.

- Volodya