[Python-Dev] devguide: Write a guide to committing a patch.

Brett Cannon brett at python.org
Tue Jan 18 20:06:16 CET 2011


On Tue, Jan 18, 2011 at 05:18, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On Tue, Jan 18, 2011 at 10:35 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
>> On Tue, 18 Jan 2011 07:14:51 +0100
>> Ezio Melotti <ezio.melotti at gmail.com> wrote:
>>> > +
>>> > +Committing Patches
>>> > +==================
>> [...]
>>> > +
>>> > +    svnmerge.py merge -r 42
>>> > +
>>> > +This will try to apply the patch to the current patch and generate a
>>> > commit
>>
>> Do we want to spend so much time explaining how to use SVN for core
>> developers while we're supposed to switch to Mercurial Real Soon Now?
>> (current core devs already know how to use it, and we don't get many
>> new ones every month)
>
> Yes, since it makes it clear where the new hg instructions need to go
> and the minimum set of operations they have to cover.

Plus it's from the dev FAQ so I didn't have to go and figure something out.


More information about the Python-Dev mailing list