On 6/1/12 3:14 AM, Bert Huijben wrote: > >> -----Original Message----- >> From: Philip Prindeville [mailto:philipp_s...@redfish-solutions.com] >> Sent: vrijdag 1 juni 2012 1:47 >> To: users@subversion.apache.org >> Subject: Issues with externals >> >> I'm using svn 1.6.11 of Centos 6.2. >> >> I've noticed the following two issues with externals. >> >> (1) If I have an external and then do a "svn propedit svn:externals ..." > and >> delete a path, the file that was previously exported into my space by "svn >> update" persists in a state of limbo. >> >> (2) An "svn merge" seems to apply svn:mergeinfo property changes to >> externals. This seems extremely unwise. Should "svn merge" (and perhaps >> other commands) skip over external files? >> >> I love externals... they're very handy for multiple projects sharing > partial >> common sources... but they aren't as easy to use as they should be, and >> come with some bizarre (non-intuitive) semantics. >> >> Is this bugworthy? > This was fixed in Subversion 1.7.0+, using the new working copy database. > > We now keep track of exactly what externals were installed during update to > allow removing them later, even when they were only referenced from > uncommitted svn:externals properties. > > Bert >
I take it there's no way to backport a fix to 1.6.x? -Philip
