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

How to undo accidental 'pinning' of sub-directories?

From: Neil Bird <neil_at_jibbyjobby.co.uk>
Date: Fri, 17 Dec 2010 10:10:15 +0000

   A colleague new to Subversion has a part of a project spread across a
number of sibling directories. He had been making some significant changes
and didn't want to “risk” doing a ‘svn update’ on the top level directory,
instead manually doing updates on the siblings of the main directory he was
working in. These piecemeal updates happened across several days, spanning
several revisions.

   When we came to make a branch for his work as ‘svn switch’ to it (at his
top-level), we found that most of the sibling directories were still linked
to their positions in trunk.

   I'm guessing that the multiple individual updates ‘pinned’ the siblings
to the respective revision of the update as if a a ‘svn switch’ had been done.

   Given that where we ended up was a mess of our (well, his) own devising,
I'm left wondering what the best recovery would have been? I had to
manually ‘svn-switch’ the sibling dirs., sort out the commit, then clear out
the whole lot with a fresh checkout (well, I actually set the root depth to
“only” followed by “infinity” to reset it).

   In general, if you have a hierarchy that may have had some switches
(etc.) applied at arbitrary locations within it, is there a way to enforce
an update at the top level that undoes the switches (without blowing it all
away and re-creating the working copy, as there may be local changes)?

[neil_at_fnx ~]# rm -f .signature
[neil_at_fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil_at_fnx ~]# exit
Received on 2010-12-17 11:10:57 CET

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

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