On Sun, Mar 11, 2012 at 1:10 PM, Andreas Krey <a.krey_at_gmx.de> wrote:
>> That seems wrong or at least unnecessarily inconvenient for a CI
> You're a bit hung up on the 'CI' token. That isn't the only situation
> where a 'svn cleanup' can be useful.
Subversion probably isn't the best VCS to use if you can't arrange
reasonable connectivity to the repository to make clean checkouts
>> And if you are doing it by hand, why not just delete
>> everything but your .svn directory and revert?
> Typical VCS operations should not only be possible but also easy.
> (And even the 'everything but .svn' part is tricky.)
With post-1.7 versions, it shouldn't be hard at all - at least on
systems where filenames starting with '.' don't expand in wildcards.
But, if I know I'm going to want to return to a particular
working-copy state, I just copy the whole thing locally before making
the changes I may want to discard. I'd be more likely to do that to
preserve a set of local changes that I wasn't sure about committing or
to hold a checkpoint offline like you might in a distributed VCS, but
it should work as well to have an 'already reverted' copy sitting
locally when bandwidth is a concern. This isn't particularly optimal
with subversion either since you end up with two full copies of
everything in each instance of the working copies, but at least it
gives you a choice of disk or network resources.
Received on 2012-03-11 19:41:50 CET