From: Christian Hesse <list@eworm•de>
To: Kousik Sanagavarapu <five231003@gmail•com>
Cc: git@vger•kernel.org,
Christian Couder <christian.couder@gmail•com>,
Hariom Verma <hariom18599@gmail•com>,
Junio C Hamano <gitster@pobox•com>
Subject: Re: [PATCH v2 1/1] t6300: fix match with insecure memory
Date: Tue, 22 Aug 2023 15:01:49 +0200 [thread overview]
Message-ID: <20230822150149.541ccb35@leda.eworm.net> (raw)
In-Reply-To: <20230822110404.1c002dcf@leda.eworm.net>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
Christian Hesse <list@eworm•de> on Tue, 2023/08/22 11:04:
> So we need a set of commands to bring the output of both command in line,
> with or without warning on insecure memory.
I think I found a clean solution... Running a trustdb update earlier
makes the extra lines go away, and we do not need to filter them. See
the follow up...
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-08-22 13:01 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 [this message]
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 ` [PATCH " Junio C Hamano
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=20230822150149.541ccb35@leda.eworm.net \
--to=list@eworm$(echo .)de \
--cc=christian.couder@gmail$(echo .)com \
--cc=five231003@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=hariom18599@gmail$(echo .)com \
/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