simon-git: putty (main): Simon Tatham

[Commits to Tartarus hosted VCS]

TL;DR:
  7802932e Document how to set GIT_SSH_COMMAND to plink -batch.
  c91437ba Update cmake_minimum_required to avoid warnings on sid.

Repository:     https://git.tartarus.org/simon/putty.git
On the web:     https://git.tartarus.org/?p=simon/putty.git
Branch updated: main
Committer:      Simon Tatham <anakin at pobox.com>
Date:           2024-12-15 11:18:18

commit 7802932eed5bcf5890ed50718eced0c9fbb424bf
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=7802932eed5bcf5890ed50718eced0c9fbb424bf;hp=09095a7d9261676871a881aff7df4b39bd2802b4
Author: Simon Tatham <anakin at pobox.com>
Date:   Sun Dec 15 09:59:22 2024 +0000

    Document how to set GIT_SSH_COMMAND to plink -batch.
    
    A user helpfully figured this out for us after the changes to Plink's
    password prompt handling had disrupted their previous workflow. So it
    seems worth documenting in case anyone else needs this fix.
    
    (I think it is a fix, not a workaround: anyone needing this option now
    probably _should_ have been doing it all along, because with the old
    behaviour, Plink would have been sending a password prompt to Git, and
    maybe even interpreting some of Git's protocol output as a password!
    -batch would have been a more sensible way to abort the connection
    even before the changes.)

 doc/plink.but | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)

commit c91437bae3a9aef1e235a0dc00669dc91a76c6e3
web diff https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=c91437bae3a9aef1e235a0dc00669dc91a76c6e3;hp=7802932eed5bcf5890ed50718eced0c9fbb424bf
Author: Simon Tatham <anakin at pobox.com>
Date:   Sun Dec 15 10:16:01 2024 +0000

    Update cmake_minimum_required to avoid warnings on sid.
    
    The new (ish) "3.7...3.28" syntax means: cmake will give up with a
    fatal error if you try to build with a version older than 3.7, but
    also, it won't turn on any new behaviour introduced after 3.28 (which
    is the cmake version in Ubuntu 24.04, where I'm currently doing both
    my development and production builds).
    
    Without this, cmake 3.31 (found on Debian sid) will give a warning at
    configure time: "Compatibility with CMake < 3.10 will be removed from
    a future version of CMake." I guess the point is that they're planning
    to make breaking changes that arrange that you _can't_ make the same
    CMakeLists work with both 3.7 and this potential newer version. So by
    specifying 3.28 as the "max" version, we avoid those breaking changes
    affecting us, for the moment.
    
    Our "old distro support" policy is currently that we still want to be
    able to (and indeed I actually test it before each release) build on
    Debian stretch, which is still in support, albeit a very marginal
    paid-LTS kind of support. So we do still need to support cmake 3.7.
    This seems to be a plausible way to get that to carry on working,
    while not provoking annoying warnings from cmake 3.31, or risking the
    actual breaking change when it comes, whatever it is.
    
    (Fun fact: cmake 3.7 doesn't actually _understand_ this 3.7...3.28
    syntax! That syntax itself was introduced in 3.12. But the cmake
    manual explains that it's harmless to earlier versions, which will
    interpret the extra dots as separating additional version components,
    and ignore them. :-)

 CMakeLists.txt            | 2 +-
 doc/CMakeLists.txt        | 2 +-
 test/sclog/CMakeLists.txt | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)