All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Christian Hesse <list@eworm.de>,
	Git Mailing List <git@vger.kernel.org>,
	Kousik Sanagavarapu <five231003@gmail.com>,
	Christian Couder <christian.couder@gmail.com>,
	Hariom Verma <hariom18599@gmail.com>,
	Christian Hesse <mail@eworm.de>
Subject: Re: [PATCH 2/2] t/t6300: drop magic filtering
Date: Wed, 23 Aug 2023 09:02:00 -0700	[thread overview]
Message-ID: <xmqq8ra1hhmv.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cTFrroZGo=KOXu0aCxeJvNz7eaHAK++HXELZ0ZheJhw9w@mail.gmail.com> (Eric Sunshine's message of "Tue, 22 Aug 2023 12:43:22 -0400")

Eric Sunshine <sunshine@sunshineco.com> writes:

> On Tue, Aug 22, 2023 at 9:03 AM Christian Hesse <list@eworm.de> wrote:
>> Now that we ran a trustdb check forcibly it does no longer pullute the
>> output. Filtering is no longer required...
>
> s/pullute/pollute/
>
>> Signed-off-by: Christian Hesse <mail@eworm.de>

Thanks.  Applied the typofix (with removal of the extra double-dots)
while queuing.

  parent reply	other threads:[~2023-08-23 16:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 20:06 [PATCH 1/1] t6300: fix match with insecure memory Christian Hesse
2023-08-21 20:24 ` Christian Hesse
2023-08-21 20:25   ` [PATCH v2 " Christian Hesse
2023-08-22  7:54     ` Kousik Sanagavarapu
2023-08-22  9:04       ` Christian Hesse
2023-08-22 13:01         ` Christian Hesse
2023-08-22 13:03           ` [PATCH 1/2] t/lib-gpg: forcibly run a trustdb update Christian Hesse
2023-08-22 13:03             ` [PATCH 2/2] t/t6300: drop magic filtering Christian Hesse
2023-08-22 16:43               ` Eric Sunshine
2023-08-23  6:52                 ` [PATCH v2 " Christian Hesse
2023-08-23 13:20                   ` Kousik Sanagavarapu
2023-08-23 16:14                     ` Junio C Hamano
2023-08-23 16:02                 ` Junio C Hamano [this message]
2023-08-22 15:50         ` [PATCH v2 1/1] t6300: fix match with insecure memory 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=xmqq8ra1hhmv.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=five231003@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hariom18599@gmail.com \
    --cc=list@eworm.de \
    --cc=mail@eworm.de \
    --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 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.