<br><br><div class="gmail_quote">On Fri, Mar 21, 2008 at 6:12 PM, Brett Cannon <<a href="mailto:brett@python.org">brett@python.org</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;">
On Fri, Mar 21, 2008 at 3:10 PM, Benjamin Peterson<br>
<div class="Ih2E3d"><<a href="mailto:musiccomposition@gmail.com">musiccomposition@gmail.com</a>> wrote:<br>
><br>
><br>
><br>
><br>
> 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>
> ><br>
> > 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<br>
> it.<br>
> > > The history is saved in the repository so it's efficient.<br>
> ><br>
> > 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.<br>
> Yes, bzr diff should do the trick, although if you have local commits in it,<br>
> you'll have to give the revision number manually.<br>
<br>
</div>That's not really true. Let's say you have a trunk branch that you<br>
keep which is pristine. You branch off of it and create a xxx branch.<br>
You can diff between xxx and trunk by running ``bzr diff xxx --old<br>
trunk``. You can also run this from within xxx with ``bzr diff --old<br>
../trunk``.</blockquote><div>Well, I just learned something. ;) <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>
-Brett<br>
</font></blockquote></div><br>