git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Adam Szkoda <adaszko@gmail.com>
Cc: Adam Szkoda via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org, Phillip Wood <phillip.wood123@gmail.com>,
	Fabian Stelzer <fs@gigacodes.de>
Subject: Re: [PATCH v2] ssh signing: better error message when key not in agent
Date: Wed, 25 Jan 2023 09:17:50 -0800	[thread overview]
Message-ID: <xmqqsffyedoh.fsf@gitster.g> (raw)
In-Reply-To: <CAEroKagUY5PfuC2CDn=pTJ=brPsjPy6MVz54mH1tvN8E-Pvk7g@mail.gmail.com> (Adam Szkoda's message of "Wed, 25 Jan 2023 13:46:36 +0100")

Adam Szkoda <adaszko@gmail.com> writes:

>> We do
>> not pass filename yet with this pushl(), because ...
>>
>> > +     if (literal_ssh_key) {
>> > +             strvec_push(&signer.args, "-U");
>> > +     }
>>
>> ... when we give a literal key, we want to insert "-U" in front, and then
>>
>> > +     strvec_push(&signer.args, buffer_file->filename.buf);
>>
>> ... the filename.  Which makes sense.
>
> I'm not sure what you mean in this paragraph.   If there's something
> more that needs to be done, I'd appreciate it if you could rephrase
> it.

"Which makes sense." is the key conclusion.  Instead of saying "This
part of the patch looks good" without explaining why I say so (it
could be that I am saying so without really reading or understanding
the changes or thinking the ramifications of the change through),
the earlier parts that lead to the conclusion is a way to give
weight to the conclusion.

In other words, it is meant to show that the reviewer did read the
patch well enough to understand the reasoning behind it.

Thanks.

  parent reply	other threads:[~2023-01-25 17:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18  8:17 [PATCH] ssh signing: better error message when key not in agent Adam Szkoda via GitGitGadget
2023-01-18 11:10 ` Phillip Wood
2023-01-18 14:34   ` Phillip Wood
2023-01-18 15:28     ` Adam Szkoda
2023-01-18 16:29       ` Phillip Wood
2023-01-20  9:03         ` Fabian Stelzer
2023-01-23  9:33           ` Phillip Wood
2023-01-23 10:02             ` Fabian Stelzer
2023-01-23 16:17               ` Adam Szkoda
2023-01-24 15:26 ` [PATCH v2] " Adam Szkoda via GitGitGadget
2023-01-24 17:52   ` Junio C Hamano
2023-01-25 12:46     ` Adam Szkoda
2023-01-25 17:04       ` Junio C Hamano
2023-01-25 17:17       ` Junio C Hamano [this message]
2023-01-25 21:42       ` Eric Sunshine
2023-01-25 22:22         ` Junio C Hamano
2023-02-15  1:22           ` Eric Sunshine
2023-01-25 12:40   ` [PATCH v3] " Adam Szkoda via GitGitGadget

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=xmqqsffyedoh.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=adaszko@gmail.com \
    --cc=fs@gigacodes.de \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=phillip.wood123@gmail.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).