[issue13963] dev guide has no mention of mechanics of patch review

[Ezio Melotti]

Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Most of the patches are against 3.2 or 2.7, so applying them to "default" might fail.
If we specify the correct branch, rietveld should be able to apply them cleanly to the head of the branch even without knowing the exact revision (so even with git-style diff).  This might still fail if the files affected by the patch changed in the meanwhile, but that shouldn't happen very often.
If this is true, we could simply add a way to specify the branch (either a dropdown in the roundup UI or an X.Y in the filename).  This might also be used to avoid conflicts when the same patch is submitted for different branches.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13963>
_______________________________________