Am 08.03.2011 11:19, schrieb Antoine Pitrou: > On Tue, 08 Mar 2011 09:38:27 +0100 > "Martin v. Löwis"<martin at v.loewis.de> wrote: >>> However, as Michael points out, you can have your tools generate the >>> patch. For example, it shouldn't be too hard to add a dynamic patch >>> generator to Roundup (although I haven't thought about the UI or the >>> CPU burden). >> >> For Mercurial, that's more difficult than you might expect. There is "hg >> incoming -p", but it has the nasty problem that it may produce >> multiple patches for a single file. > > If you use named branches it's trivial, and it's suggested in the > devguide in > http://docs.python.org/devguide/committing.html#long-term-development-of-features That requires a local repository, right? Plus it requires knowing the branch name, which makes it difficult for automated patch generation. Regards, Martin
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