git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, rjusto@gmail.com, sunshine@sunshineco.com
Subject: Re: [PATCH v2] doc: imply that interactive.singleKey is disabled by default
Date: Sat, 08 Jun 2024 11:59:38 +0200	[thread overview]
Message-ID: <0a3e229942b314947b3a301a85cfef8c@manjaro.org> (raw)
In-Reply-To: <xmqqbk4ce6w3.fsf@gitster.g>

Hello Junio,

On 2024-06-08 00:15, Junio C Hamano wrote:
> Dragan Simic <dsimic@manjaro.org> writes:
> 
>> On 2024-06-01 00:21, Dragan Simic wrote:
>>> On 2024-05-31 19:23, Junio C Hamano wrote:
>>>> Dragan Simic <dsimic@manjaro.org> writes:
>>>>> Just checking, is there something left to be addressed for this
>>>>> patch,
>>>>> before it can be considered to be pulled into the next branch?
>>>> Thanks for pinging, as these small things were on the back burner
>>>> while preparing for updates to maintenance tracks.
>>>> Apparently v2 cannot be pulled into the next branch, and I forgot
>>>> if
>>>> I saw v3 already.  In general, unless I explicitly say there is no
>>>> need to resend (sometimes with conditions), I'd expect an updated
>>>> iteration sent to the list.
>>> I see, but I'm not really sure is there need for the v3?  Maybe the
>>> patch description could be tweaked a bit further, but I wasn't under
>>> impression that you asked for that to be done?  Am I wrong there?
>> 
>> Any chances, please, to have a look at this?
> 
> I _have_ taken a look---as I said, "I saw v3 already".
> 
> Unless you were asking other folks, that is, but the message was
> addressed to me with others CC'ed, so I am not sure what the true
> intention was.

Ah, I see now [1] what you asked for, which was a slight rewording
of the patch subject and description.  That's what my intention was,
to check was rewording the patch v2 subject and description necessary.
Sorry for the confusion, and thanks for putting the v3 [1] together.

[1] https://lore.kernel.org/git/xmqq4ja4e6d6.fsf@gitster.g/

  reply	other threads:[~2024-06-08  9:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 21:24 [PATCH v2] doc: imply that interactive.singleKey is disabled by default Dragan Simic
2024-05-22 21:31 ` Junio C Hamano
2024-05-22 21:34   ` Dragan Simic
2024-05-31  0:49     ` Dragan Simic
2024-05-31 17:23       ` Junio C Hamano
2024-05-31 22:21         ` Dragan Simic
2024-06-04 20:11           ` Dragan Simic
2024-06-07 22:15             ` Junio C Hamano
2024-06-08  9:59               ` Dragan Simic [this message]
2024-06-07 22:27 ` [PATCH v3] doc: " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0a3e229942b314947b3a301a85cfef8c@manjaro.org \
    --to=dsimic@manjaro.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rjusto@gmail.com \
    --cc=sunshine@sunshineco.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.
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 NNTP newsgroup(s).