[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] svnadmin freeze r1 svnadmin freeze r2 rsync -a ./

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Mon, 7 Apr 2014 17:50:31 +0000

Julian Foad wrote on Mon, Apr 07, 2014 at 11:36:57 +0100:
> Daniel Shahaf wrote:
> > Is this a good idea? ---
> Sure -- why not?

Because I wasn't sure whether that's a supported use-case or something
that just happens to work --- compare --editor-cmd='f(){ x=$0; echo
"Template text" > "$0"; $EDITOR "$0" }; f'.

> > [[[
> > Test that 'svnadmin freeze' is nestable.
> >
> > This would be useful in practice as a means to easily freeze a (small)
> > number of repositories simultaneously.  It also verifies that 'freeze'
> > doesn't take system-global locks.
> Please put this documentation of the test's purpose in the test itself.


> > On re-reading the code, I wonder if I should add read_only=True to
> > sbox.create().. this would cause the code to freeze the shared read-only
> > repository, which shouldn't affect other tests in any way except perhaps
> > to slow them down (when BDB is in use).
> No. Keep tests independent. Anyway, this requires a kind of write access to the repo it freezes.

"Kind of" read access. It doesn't create or otherwise modify history.
It won't step on the feet of other tests that use the pristine
repository (whether to read its history or to freeze it). That's why I
wasn't sure.

Thanks for the review; committed r1585535.

Received on 2014-04-07 19:51:09 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.