<div>On 12/1/06, Nicholas Allen <<a href="mailto:allen@ableton.com">allen@ableton.com</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> ... bzr push mainline Error: The destination branch location is a shared branch and your push will reorder the revisions. You should use a checkout/bound branch in order to commit changes to this location. You can make this branch a bound branch by running 'bzr bind mainline'. You will then need to update your branch by running 'bzr update'. Then you can run bzr commit to commit your changes to this location. Then there would be no need for a --to option added to the merge command. This would also be something that could be implemented easily and would work even without smart server support on dumb file servers. </blockquote> </div> I think you should not force the user to bind to the branch, he might work off-line a lot and do lots of local commits, it will be nice to allow him this functionality without requiring him to bind, this might be where the --to could be usefull regards mairus -- I code therefore I am.