[issue12101] PEPs should have consecutive revision numbers

2011-05-29 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: This request is not feasible with Mercurial and the useful info is already available. Closing. -- resolution: - works for me stage: - committed/rejected status: open - closed ___ Python tracker

[issue12101] PEPs should have consecutive revision numbers

2011-05-23 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: IOW, invalid? -- components: +None -Devguide nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12101 ___

[issue12101] PEPs should have consecutive revision numbers

2011-05-18 Thread Georg Brandl
Georg Brandl ge...@python.org added the comment: 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

[issue12101] PEPs should have consecutive revision numbers

2011-05-17 Thread anatoly techtonik
New submission from anatoly techtonik techto...@gmail.com: 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