All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Kilian Kilger via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Tao Klerks <tao@klerks.biz>,
	Kilian Kilger <kkilger@gmail.com>
Subject: Re: [PATCH v3 0/2] git-p4: Fix bug with encoding of P4 client name
Date: Thu, 21 Jul 2022 09:46:25 -0700	[thread overview]
Message-ID: <xmqqr12ejtwe.fsf@gitster.g> (raw)
In-Reply-To: <pull.1285.v3.git.git.1658394440.gitgitgadget@gmail.com> (Kilian Kilger via GitGitGadget's message of "Thu, 21 Jul 2022 09:07:18 +0000")

"Kilian Kilger via GitGitGadget" <gitgitgadget@gmail.com> writes:

> Kilian Kilger (2):
>   git-p4: fix bug with encoding of p4 client name
>   git-p4: refactoring of p4CmdList()

[PATCH v3 1/2] seems to be identical to 34f67c96 (git-p4: fix bug
with encoding of p4 client name, 2022-07-08) that was already merged
to 'next' yesterday, so I can safely ignore it and take [PATCH v3
2/2] as if it were a single follow-up patch on the same topic and
queue it on top.

Thanks.

      parent reply	other threads:[~2022-07-21 16:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08  8:01 [PATCH] git-p4: fix bug with encoding of p4 client name Kilian Kilger via GitGitGadget
2022-07-08 11:28 ` Tao Klerks
2022-07-08 15:05   ` Junio C Hamano
2022-07-18  8:57 ` [PATCH v2] " Kilian Kilger via GitGitGadget
2022-07-18 16:36   ` Junio C Hamano
2022-07-21  9:07   ` [PATCH v3 0/2] git-p4: Fix bug with encoding of P4 " Kilian Kilger via GitGitGadget
2022-07-21  9:07     ` [PATCH v3 1/2] git-p4: fix bug with encoding of p4 " Kilian Kilger via GitGitGadget
2022-07-21  9:07     ` [PATCH v3 2/2] git-p4: refactoring of p4CmdList() Kilian Kilger via GitGitGadget
2022-07-21 16:46     ` Junio C Hamano [this message]

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=xmqqr12ejtwe.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=kkilger@gmail.com \
    --cc=tao@klerks.biz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.