[issue23942] Explain naming of the patch files in the bug tracker

Ezio Melotti added the comment: I think this is not worth fixing, for two reasons: 1) we are moving away from Rietveld; 2) even if we document it, most people won't go looking for naming conventions and just use reasonable names (and most of the times they will just work); I'm therefore going to

[issue23942] Explain naming of the patch files in the bug tracker

Martin Panter added the comment: I guess if people wonder about this, you could at least say the naming doesn’t matter very much for the review system. If I am generating my own patches, I try to name them with one or two concise words describing the particular solution, and then insert “.v2”,

[issue23942] Explain naming of the patch files in the bug tracker

Changes by R. David Murray : -- nosy: -r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue23942] Explain naming of the patch files in the bug tracker

Maciej Szulik added the comment: Ezio, I've meant we should provide some guidelines with information the system will pick whatever they choose based on submission date. More informational than as a requirement. -- ___ Python tracker

[issue23942] Explain naming of the patch files in the bug tracker

Ezio Melotti added the comment: FWIW I use e.g. issue1234.diff and if further patches are needed I add an increasing suffix: issue1234-2.diff, issue1234-3.diff, etc. Since the name doesn't matter too much, I'm not sure it's worth documenting and/or enforcing a specific convention. -- n

[issue23942] Explain naming of the patch files in the bug tracker

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