On Tue, Mar 22, 2011 at 9:02 AM, Guido van Rossum <gu...@python.org> wrote: > On Mon, Mar 21, 2011 at 5:10 PM, Éric Araujo <mer...@netwok.org> wrote: >> Le 13/03/2011 19:03, "Martin v. Löwis" a écrit : >>> 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). >> >> These features are truly excellent. Well done, sir, and thank you! > > I'm having a hard time discovering how to use the feature (though I > think I've seen issues using it). What's the magical UI?
Have a look at this issue: http://bugs.python.org/issue11591 The magical UI is the FORM textbox element "Remote hg repo:" where the user provided his bitbucket URL for the path he was working on. And when you pressed "Create Patch" button, it created a patch and then attached to the issue tracker. You can click on the review button to post that patch to reitveld and do the review,. Also somewhere else, it was mentioned that hg import can take a remote url of the patch and import it directly. (If we want, portion can be bit automated in the future to take latest patch if we provide the issue #) So, it all becomes super cool. But, I have a couple of doubts in this magic, which I think MvL can shed some light - In the above issue, why is two same bitbutket urls are provided. (It is redundant). - Also, how is it that system is creating patch from a repository outside of hg.python.org? What if the user had an older version in remote repo and tip in the hg.python.org has moved forward? -- Senthil _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
