<br><br><div class="gmail_quote">On Fri, Mar 21, 2008 at 5:04 PM, Paul Moore <<a href="mailto:p.f.moore@gmail.com">p.f.moore@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On 21/03/2008, Benjamin Peterson <<a href="mailto:musiccomposition@gmail.com">musiccomposition@gmail.com</a>> wrote:<br>
> I tend to make a repository and make a working copy for each patch in it.<br>
> The history is saved in the repository so it's efficient.<br>
<br>
</div>OK, so just lots of copies, fair enough. Presumably just use bzr diff<br>
to create patches? Much like Subversion, in practice, but with local<br>
commits of partial work.</blockquote><div>Yes, bzr diff should do the trick, although if you have local commits in it, you'll have to give the revision number manually. Bazaar also has this cool feature called merge directives. They let you bundle your branch (with all the commits) in a patch-like file, which can be easily merged into the mainline by core devs. Of course, Python hasn't moved to Bazaar, so widespread use of those is unlikely soon.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<font color="#888888"><br>
Paul.<br>
</font></blockquote></div><br>Cheers,<br>Benjamin Peterson<br>