simon-git: putty-wishlist (master): Simon Tatham

[Commits to Tartarus CVS repository.]

TL;DR:
  e3de06b Stop misidentifying git commit hashes as PuTTY releases.
  02af007 Reverse-order the release sections on the wishlist page.

Repository:     git://git.tartarus.org/simon/putty-wishlist.git
On the web:     http://tartarus.org/~simon-git/gitweb/?p=putty-wishlist.git
Branch updated: master
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2015-03-08 08:29:05

commit e3de06b29fa2caaa992e130d9cb0564476207113
web diff http://tartarus.org/~simon-git/gitweb/?p=putty-wishlist.git;a=commitdiff;h=e3de06b29fa2caaa992e130d9cb0564476207113;hp=363d2195f587b4d6c896af3e875955fae29f805d
Author: Simon Tatham <anakin at pobox.com>
Date:   Sun Mar 8 08:20:34 2015 +0000

    Stop misidentifying git commit hashes as PuTTY releases.
    
    The Wishlist page currently contains a section with the heading 'Fixed
    in release 7d97c2a8fdb745905fd61a9ce4abbf822e167cef', because I
    entered that commit id in the Fixed-in header for spew-lockup-2.
    
    git commit hashes in Fixed-in should be informational only - they
    should show up in the individual bug pages, but play no part in the
    formatting of the main Wishlist page.

 control/bugs2html |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

commit 02af00781e2d99db8ddd2692e32aaaa4a20b72db
web diff http://tartarus.org/~simon-git/gitweb/?p=putty-wishlist.git;a=commitdiff;h=02af00781e2d99db8ddd2692e32aaaa4a20b72db;hp=e3de06b29fa2caaa992e130d9cb0564476207113
Author: Simon Tatham <anakin at pobox.com>
Date:   Sun Mar 8 08:26:05 2015 +0000

    Reverse-order the release sections on the wishlist page.
    
    It's becoming far too silly to have the most important parts of the
    page - which bugs are fixed in the latest release, or still exist in
    the latest release but are fixed in the snapshots - be _half way down_
    the page, between all the historical info about very old releases and
    the still-unfixed wishlist section.
    
    So I've reordered those sections to put the latest releases at the top
    and the old ones down at the bottom. This wasn't just a question of
    prefixing 'reverse' to the 'sort' in the main loop, because the
    'Broken and fixed between' section was implemented by remembering the
    last thing we saw going round the loop, so I also had to move that
    around and swap $oldclass with $class in its code.

 control/bugs2html |   55 ++++++++++++++++++++++++++---------------------------
 1 file changed, 27 insertions(+), 28 deletions(-)