[Python-Dev] Submitting changes through Mercurial

[Éric Araujo]

Le 22/03/2011 22:47, Nick Coghlan a écrit :
> On Tue, Mar 22, 2011 at 10:53 PM, Éric Araujo <merwok at netwok.org> wrote:
>> You have to use one public repo per bug, as roundup will only use the
>> default branch to compute the diff.  Maybe adding support for named
>> branches so that you can have one repo used for many bug reports would
>> be useful.
> Since I run my sandbox that way, I asked Martin about that at Pycon -
> it's on his todo list for the integration.

Work has been started on that, thanks!  Roundup should soon support the
workflow described in the devguide for feature work, which will be awesome.

I’ve tried to use a clone with a named branch for
http://bugs.python.org/issue5845 and found those bugs:
- The revset code is not robust against an hyphen in the branch name.
- The first patch was empty (note that the repo was not up to date).
- After pulling, merging and pushing, the patch created contained the
merge diff, not the useful diff with my changes.

Another thing to make it rock more: In the repo list, use “#” instead of
“:” as a separator between repo URI and branch name; it’s standard
Mercurial form and will allow people to copy-paste the whole thing to
get a clone of the repo up to that branch.

Regards