Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Feb 9, 2017, 22:32 UTC
Message-ID: <alpine.DEB.2.20.1702092329440.3496@virtualbox>
In-Reply-To: <xmqqk28znhtx.fsf@gitster.mtv.corp.google.com>

Hi Junio,

On Thu, 9 Feb 2017, Junio C Hamano wrote:

Show 7 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > ... and even go so far as calling your patch reverting my refactoring
> > a hot-fix, why don't you just go ahead and merge the result over my
> > objections?
> 
> At this point, you are simply being silly.

How is it that this patch cannot be applied when, and if, that hypothetical config setting is introduced?

Maybe I am dense here, but I would really like to know why this preparatory patch must be applied *now*, when there is nothing to prepare for.

> Isn't "Putty is not a command but is also handled as if it is a valid
> implementation of SSH" a bug?

If you think it is a bug to handle an ssh command called "putty" as if it were plink, sure. I do not think there is a valid use case, but hey.

Ciao, Johannes