Le 22/03/2011 22:47, Nick Coghlan a écrit :
On Tue, Mar 22, 2011 at 10:53 PM, Éric Araujo mer...@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
Work has been started on that, thanks! Roundup should soon support the
workflow described in the devguide for feature work, which will be awesome.
Make sure to submit issues to the meta tracker, please.
I’ve tried to use a clone with a named branch for
http://bugs.python.org/issue5845 and
Make sure to submit issues to the meta tracker, please.
Right, I’ll do that. Since you have questions in this message, for now
I’ll continue here.
- The first patch was empty (note that the repo was not up to date).
This I don't understand. What repo was not up to date?
I mean that my
I mean that my linked repo didn’t have all changesets from
hg.python.org/cpython. I don’t think it should matter, but I don’t know
why the diff was empty, so I thought this information might help.
[...]
See http://bugs.python.org/file21398/c43e264256e4.diff : this
corresponds to a merge I
I see what happened: my revspec couldn't cope with the fact that you
branched fix5845 off rlcompleter-config.
Ah, I hadn’t thought of that. (I had to branch because of the former
issue with the hyphen; this is a pathological case.)
In any case, I have now changed the revspec to use Baptiste's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Senthil,
On 03/21/2011 09:57 PM, Senthil Kumaran wrote:
- In the above issue, why is two same bitbutket urls are provided. (It
is redundant).
I updated the patch, and the second time around the remote hg repo box
was empty. I wasn't sure what
I've added a feature in the bug tracker where submitters can post
Mercurial repository URLs, and then repeatedly create patches. Roundup
will extract the current patch (cpython-default:submitter-default),
and attach the patch to the issue (which then allows Rietveld review
of the patch).
