On Fri, 2009-04-03 at 01:00 +0000, Andrew Bennetts wrote:
> This is probably due to a get_stream RPC with an "ancestry-of" argument
> failing on a stacked branch?
>
> What ought to happen is fetching all the ancestry that the stacked
> branch has, then asking the fallback location for the ancestry of all
> the revisions that were referenced (but not present) in the first repo.
I think its a broken repository; perhaps due to the known stacking
issues that early bzr stacking support had?
On Fri, 2009-04-03 at 01:00 +0000, Andrew Bennetts wrote:
> This is probably due to a get_stream RPC with an "ancestry-of" argument
> failing on a stacked branch?
>
> What ought to happen is fetching all the ancestry that the stacked
> branch has, then asking the fallback location for the ancestry of all
> the revisions that were referenced (but not present) in the first repo.
I think its a broken repository; perhaps due to the known stacking
issues that early bzr stacking support had?
-Rob