public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Patrick Steinhardt <ps@pks•im>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] connect: plug protocol capability leak
Date: Mon, 08 Dec 2025 22:37:37 +0900	[thread overview]
Message-ID: <xmqqecp5ksbi.fsf@gitster.g> (raw)
In-Reply-To: <aTZ9iMPKLAfd-GSt@pks.im> (Patrick Steinhardt's message of "Mon, 8 Dec 2025 08:26:00 +0100")

Patrick Steinhardt <ps@pks•im> writes:

>> +++ b/t/t5565-push-multiple.sh
>
> Nit: we have several tests in t5505 that are related to push groups, so
> we might want to add this new test over there. I don't care too much
> though, so please feel free to ignore this nit.

I did notice the one that adds configuration but it did not look
like it is actually pushing there.  In fact, I think 5505 is more
about "git remote" futzing with the configuration that defines
various attributes of remote, not about the push or fetch operations
that are carried out using these remote definitions.

  reply	other threads:[~2025-12-08 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-07  4:40 [PATCH] connect: plug protocol capability leak Junio C Hamano
2025-12-08  7:26 ` Patrick Steinhardt
2025-12-08 13:37   ` Junio C Hamano [this message]
2025-12-08 20:18 ` Jeff King

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=xmqqecp5ksbi.fsf@gitster.g \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=ps@pks$(echo .)im \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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