On Mon, 2008-02-18 at 20:33 +0000, Colin Watson wrote: > 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
I understand svn's behaviour here. But bzr is not svn, and the behaviour of bzr-svn in this situation is consistent with the behaviour bzr itself would show if your homedir was versioned. So it is entirely irrelevant how the svn UI behaves - because you're not using the svn UI. Running 'bzr add' in an unversioned directory of a tree bzr is able to modify, will add that directory, and its parents, until it encounters the closest versioned directory. > Therefore, 'bzr add' shouldn't try to treat this environment as part of > a Subversion working copy either. If bzr was svn I would agree with you. The more I think about this the more 'its operating as designed' as far as I can tell. 'bzr st' in an unversioned subdir of a bzr tree will give that trees status. If the tree happens to be a foreign tree the end user behaviour should be the same, and bzr-svn is doing the right thing. > 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. Its a shame you needed to do this. This may indicate that the bzr UI in unversioned subdirectories is inappropriate, rather than being a bzr-svn specific issue. if thats the case we can look at how to change it (and from there how to tweak the interface so bzr-svn doesn't trigger network activity etc like it is). -Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>. > -- 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
