Request: bzr send --complete

[Nathan Adams]

It is sometimes necessary to propagate revision history to repositories that do not have access to the source repository (image having repositories on two physically separate networks). To accomplish this, a bundle could be used.

HOWEVER when creating the bundle from the source repo, a submit branch must either be specified or the parent is assumed. In this particular use case both are wrong since the true target lives on a physically separate network. The result is that the bundle often lacks the complete revision data desired. Attempting to merge the bundle into the target branch results in the dreaded "ERROR Revision x not present in "<bzrlib.knit.KnitGraphIndex object at 0x0200000000012281d>".

Adding a "--complete" option would solve this. This option would ignore the relative state of the submit repo and assume that all revision data (within the specified revision range, as applicable) would be placed in the bundle.

[John A Meinel (jameinel)]

bundle-revisions is deprecated over 'send'. You still need to specify a submit branch, though you can specify an empty branch
bzr init empty-branch
cd mybranch
bzr send ../empty-branch -o whole-content.patch

Will give you the whole ancestry.

I'd prefer if

bzr send -r X..Y --complete

would also send all of the content for X..Y without having to specify a submit branch. (Or just do so if a submit branch is not specified.)