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. 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. > > > Paul. > Cheers, Benjamin Peterson -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20080321/354dce99/attachment.htm
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