On Mon, Nov 16, 2009 at 9:39 AM, Vladimir Prus <vladimir@codesourcery.com> wrote:
Beman Dawes wrote:
On Sun, Nov 15, 2009 at 8:11 PM, Robert Ramey <ramey@rrsd.com> 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.
Interesting. But it is a bit more complex than that due to the need to do separate Unix line ending and Windows line ending exports. I'll explore further.
(The ^ syntax works only if you're in a working copy).
I'm only beginning to wrap my mind around the ^ syntax. It seems quite useful.
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.
Thanks, --Beman