[Svnmerge] init leakage

[James Sleeman]

My repository looks like (in order of creation and svnmerge init'ing):
 /trunk

 /client/foo
 /site/bar

 /client/zort
 /site/narf

client/foo is a (bi-directional) branch of trunk, and has been init'd
against it.
site/bar is a (bi-directional) branch of client/foo, and has been init'd
against it.
client/zort is a (bi-directional) branch of trunk, and has been init'd
against it.
site/narf is a (bi-directional) branch of client/zort, and has been
init'd against it.

If I do svnmerge avail in site/narf I get both zort (correct) and foo
(incorrect) and trunk (also incorrect).

It only seems to propogate forwards, not backwards.  That is, if I do
svnmerge avail in site/bar I do not get client/zort which was init'd
after site/bar was.

Is it just a problem in my three-tier layout that I'm going to have to
live with, or is it something that could be fixed safely?   

NB: merge's are and have always been done with the bidirectional flag on
(I changed the default for that flag in svnmerge.py to true)


-- 
James Sleeman, Gogo Internet Services
http://host.gogo.co.nz/ - Webhosting + Free Domain or 25% Discount for Designers
http://code.gogo.co.nz/ - PHP Programming