Issue 12101: PEPs should have consecutive revision numbers (original) (raw)

Issue12101

Created on 2011-05-18 05:12 by techtonik, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg136204 - (view) Author: anatoly techtonik (techtonik) Date: 2011-05-18 05:12
Currently, PEPs have only hash number, which doesn't explain about how many changes were done to the PEP since my last review. It will be convenient to have consecutive revision number for PEP edits and link it to short history log (like wiki history) with current revision highlighted. This is useful to track when PEP on site is not updated to current version.
msg136206 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2011-05-18 07:39
The Last-Modified date should tell you just the same, without any arbitrary version numbers that don't have a meaning in hg. And behold, the Last-Modified date already links to the hg page for this PEP, from where you can select the "file log" to get to the list of changes.
msg136648 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2011-05-23 14:33
IOW, invalid?
msg137198 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2011-05-29 16:42
This request is not feasible with Mercurial and the useful info is already available. Closing.
History
Date User Action Args
2022-04-11 14:57:17 admin set github: 56310
2011-05-29 16:42:58 eric.araujo set status: open -> closedresolution: works for memessages: + stage: resolved
2011-05-23 14:33:10 eric.araujo set nosy: + eric.araujomessages: + components: + None, - Devguide
2011-05-18 07:39:24 georg.brandl set nosy: + georg.brandlmessages: +
2011-05-18 05:12:16 techtonik create