Comment 2 for bug 227340

Using "bzr send --no-bundle" _could_ work - but it has some drawbacks:

- it needs a public branch. And I needed some time to figure out, that I could also use "." as a public branch. But as you can't give the public branch as a named argument, you also have to include the submit (so: in most cases the parent) branch explicitly. - So (if you don't want to change something in .bzr/locations.conf) you need to use:

    bzr send --no-bundle $PARENT .

Which is ugly to type -- and (at least for me) "gittish" (read: overly complex)

- the mail still contains quite a bunch of metadata. This might annoy people which are not using bzr.

Whether the "to-be-written" command merges all commits into one diff or creates one diff per commit, is not really important imho. Because this can easily be controlled using a commandline switch :)

I just need a simple replacement for the "bzr diff -rthread:..-1 > some.patch && write mail && attach patch to mail" procedure :).