svn - How can apparently nested Subversion working copies be coalesced? [Equivalently: How do I add the parent directory to source control?] -
i have partially checked-out tree of sources. these incorrectly checked out commands this:
> svn co --depth=empty svn://repos/trunk . > svn co --depth=infinity svn://repos/trunk/project project > svn co --depth=infinity svn://repos/trunk/test test
of course, commands should have been like
> svn co --depth=empty svn://repos/trunk . > svn --set-depth=infinity project > svn --set-depth=infinity test
the resulting symptoms are:
> svn st ? project ? test
although
> svn info path: . url: svn://repos/trunk repository root: svn://repos repository uuid: 01234567-89ab-cdef-0123-456789abcdef revision: 1234 node kind: directory schedule: normal depth: empty > svn info project path: project url: svn://repos/trunk/project repository root: svn://repos repository uuid: 01234567-89ab-cdef-0123-456789abcdef revision: 1234 node kind: directory schedule: normal
(curiously, symptoms don't arise if first command svn co --depth=immediates svn://repos/trunk .
.)
now, reason symptoms file
./.svn/entries
does not contain entries project
, test
directories. (i can fix problem hacking directly file, i'd rather not.)
my question is:
is there subversion command 'coalesce' these working copies svn st
silent (or shows local modifications in project , test)?
i have tried various things, including
svn --set-depth=immediates --depth=empty .
but doesn't work because --depth
, --set-depth
"are mutually exclusive".
i have tried
svn --set-depth=infinity project
but doesn't work because project
interpreted relative path locally rather in repository; is, url formed after rather before application of relative path current directory.
worse still, have tried
svn --set-depth=immediates .
but has unfortunate (but correct) effect of merrily removing files.
this question more relevant circumstances describe. situation might call kind of 'fix' if wish check out parent of uppermost node checked out without having re-checkout sources exist locally, , whilst retaining local modifications.
thanks, rob.
no, coalescing such working copies not possible in supported way. make fresh checkout fix situation.
Comments
Post a Comment