From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)
Date: Thu, 9 Feb 2017 23:32:25 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1702092329440.3496@virtualbox> (raw)
In-Reply-To: <xmqqk28znhtx.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Thu, 9 Feb 2017, Junio C Hamano wrote:
> 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
next prev parent reply other threads:[~2017-02-09 22:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 22:34 What's cooking in git.git (Feb 2017, #02; Mon, 6) Junio C Hamano
2017-02-07 0:24 ` SZEDER Gábor
2017-02-07 1:17 ` Jacob Keller
2017-02-07 20:01 ` Junio C Hamano
2017-02-09 0:25 ` Stefan Beller
2017-02-09 1:01 ` Junio C Hamano
2017-02-09 3:46 ` Jeff King
2017-02-09 5:09 ` Junio C Hamano
2017-02-10 21:17 ` Junio C Hamano
2017-02-09 12:29 ` Johannes Schindelin
2017-02-09 17:20 ` Junio C Hamano
2017-02-09 20:37 ` Johannes Schindelin
2017-02-09 22:02 ` Junio C Hamano
2017-02-09 22:32 ` Johannes Schindelin [this message]
2017-02-09 16:08 ` Michael Haggerty
2017-02-09 19:18 ` Junio C Hamano
2017-02-09 19:24 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1702092329440.3496@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).