Robert Collins wrote: > further to that it may be the wrong thing to 'fix' it anyway, because to > preserve the behaviour of 'bzr add' working in a subdir, in a svn tree, it > /should/ find containing svn control directories and use the one found to add > paths.
No, I don't think that's correct. If the current directory has a .svn control directory, then it should indeed use that. However, I repeat, every versioned subdirectory of a Subversion working copy has a .svn control directory, not just the root of the tree as in Bazaar. A subdirectory of a Subversion working copy that does not itself have a .svn control directory is simply not part of that working copy as far as Subversion is concerned. 'svn add' fails in such a circumstance: svn: '.' is not a working copy svn: Can't open file '.svn/entries': No such file or directory Therefore, 'bzr add' shouldn't try to treat this environment as part of a Subversion working copy either. Thanks for the workaround. I've just removed bzr-svn for the meantime, as I don't use it very often and can just install it when I need it. -- bzr-svn is irritating when in a (non-svn) subdirectory of an svn working tree https://bugs.launchpad.net/bugs/192743 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
