"bzr send ../unrelated-branch" will send the whole ancestry

[Matt Nordhoff]

John Arbash Meinel wrote:
> It would seem like "bzr send ../unrelated-branch" should just refuse with a
> "no-common ancestor" error, rather than sending a bundle with the complete
> ancestry.
> 
> My specific case is that I set up a recursive "submit_to = bzr.dev" but it got
> confused when I went to "bzr send" a plugin. But either way, if you had a typo
> in "unrelated-branch" it would create a bundle you probably don't want to send.

I've never used 'bzr send'. Maybe if I had, the answers to these 
questions would be obvious.

Anyway, just to throw it out there...

If the target branch is empty, how should it behave?

And also, should it really be a fatal error? What about having a --force 
argument to override it, or just giving a warning or an "are you sure?" 
prompt, like with 'bzr uncommit'?
--