On Fri, Mar 21, 2008 at 3:10 PM, Benjamin Peterson <musiccomposition at gmail.com> wrote: > > > > > On Fri, Mar 21, 2008 at 5:04 PM, Paul Moore <p.f.moore at gmail.com> wrote: > > > > On 21/03/2008, Benjamin Peterson <musiccomposition at gmail.com> wrote: > > > I tend to make a repository and make a working copy for each patch in > it. > > > The history is saved in the repository so it's efficient. > > > > OK, so just lots of copies, fair enough. Presumably just use bzr diff > > to create patches? Much like Subversion, in practice, but with local > > commits of partial work. > Yes, bzr diff should do the trick, although if you have local commits in it, > you'll have to give the revision number manually. That's not really true. Let's say you have a trunk branch that you keep which is pristine. You branch off of it and create a xxx branch. You can diff between xxx and trunk by running ``bzr diff xxx --old trunk``. You can also run this from within xxx with ``bzr diff --old ../trunk``. -Brett
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4