[New-bugs-announce] [issue23942] Explain naming of the patch files in the bug tracker

Maciej Szulik report at bugs.python.org
Tue Apr 14 01:02:17 CEST 2015


New submission from Maciej Szulik:

During the lifecycle of a bug you do:
1. submit a patch
2. get a review with some comments
3. re-submit the patch

Talking to R. David Murray I got info there's no convention on naming those, I think it will be valuable to have some information in the devguide about that. 

Apparently you can either (when just fixing the patch) to stick with exactly the same name or add increasing suffix, eg. mypatch-1, mypatch-2, etc.).  Otherwise you can change the name, but the review system will be able to pick up the right patch, so you should not worry about that.

----------
components: Devguide
messages: 240800
nosy: ezio.melotti, maciej.szulik, willingc
priority: normal
severity: normal
status: open
title: Explain naming of the patch files in the bug tracker

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


More information about the New-bugs-announce mailing list