simon-git: putty (master): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  16214ea Initialise term->curr_truecolour at startup.
  f813e9f uxnet.c: don't close a socket's fd if it is -1.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: master
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2017-10-01 21:18:09

commit 16214ea0f5de7023c7e08fba57e7a49c2d518583
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=16214ea0f5de7023c7e08fba57e7a49c2d518583;hp=a4cbd3dfdb71d258e83bbf5b03a874c06d0b3106
Author: Simon Tatham <anakin at pobox.com>
Date:   Sun Oct 1 20:59:00 2017 +0100

    Initialise term->curr_truecolour at startup.
    
    Somehow I managed to miss _that_ really obvious bug in the true-
    colour patch.

 terminal.c | 1 +
 1 file changed, 1 insertion(+)

commit f813e9f937b5b6198659c8c64b3090dc3902b930
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=f813e9f937b5b6198659c8c64b3090dc3902b930;hp=16214ea0f5de7023c7e08fba57e7a49c2d518583
Author: Simon Tatham <anakin at pobox.com>
Date:   Sun Oct 1 21:05:25 2017 +0100

    uxnet.c: don't close a socket's fd if it is -1.
    
    This is harmless in principle (you just get EBADF back from close(2)
    and ignore it), but it leads to warnings in valgrind.

 unix/uxnet.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)