That might be considered a bug. I think you have to run update to get the new external. If the other externals are single revision then you could define that revision explicitly in svn:externals. Then you could run update and those externals would not change. You could even make the svn:externals change as a local modification and revert it after the update.
Michael Hartmeier <michael.hartme...@1und1.de> writes: > Yes: they both have no effect :( > > Michael > > Am 20.02.2012 15:35, schrieb Daniel Shahaf: >> Instead of >> >> svn checkout tuneup >> >> have you tried >> >> svn up --depth empty >> >> or >> >> svn up tuneup >> >> ? >> >> Michael Hartmeier wrote on Mon, Feb 20, 2012 at 14:49:54 +0100: >>> Hi, >>> >>> I have a working copy that only contains svn:externals, no "normal" >>> files or directories: >>> >>> $ svn propget svn:externals . >>> shop https://svn.schlund.de/shop/trunk >>> popups https://svn.schlund.de/popups/trunk/ >>> >>> How can I add a new external without updating the whole working copy? >>> >>> What worked with 1.6: I changed (and committed) the svn:externals to >>> >>> shop https://svn.schlund.de/shop/trunk >>> popups https://svn.schlund.de/popups/trunk/ >>> tuneup https://svn.schlund.de/tuneup/trunk/ >>> >>> and manually checked out the respective directory with >>> >>> svn co https://svn.schlund.de/tuneup/trunk/ tuneup >>> >>> However, with Subversion 1.7, this directory is shown with status "?": >>> >>> $ svn st >>> X shop >>> X popups >>> ? tuneup >>> >>> How can I fix the "tuneup" status to make it >>> >>> X tuneup >>> >>> ??? >>> >>> Any help would be apprecheated! >>> >>> Best regards, >>> >>> Michael >>> > -- Philip
