From: Taylor Blau <me@ttaylorr.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH v2 0/2] t/helper/test-tool: implement 'sha1-unsafe' helper
Date: Thu, 7 Nov 2024 16:36:04 -0500 [thread overview]
Message-ID: <Zy0yxDIgEmKtec/0@nand.local> (raw)
In-Reply-To: <20241107014737.GB961214@coredump.intra.peff.net>
On Wed, Nov 06, 2024 at 08:47:37PM -0500, Jeff King wrote:
> 2. You modified test-sha1.sh, but I've wondered if we should just
> delete that script. It is not ever invoked in the test suite AFAIK.
> If we want correctness tests, they should go into a real t[0-9]*.sh
> script (though one imagines we exercise the sha1 code quite a lot
> in the rest of the tests). And it starts with a weird ad-hoc
> performance test that doesn't really tell us much. A t/perf test
> would be better (if it is even worth measuring at all).
Yeah, I was sort of puzzled and thinking the same thing as I wrote the
patch.
I wouldn't be opposed to deleting it in the future, and certainly have
no strong feelings about keeping it around in the meantime. It just
seemed like the path of least resistance to bring it along for the
sha1-unsafe ride instead of deleting it outright.
> So I dunno. None of those are the fault of your series, but it is piling
> on yet another test-tool command.
Yeah, I think there was a fair amount of interesting discussion about
possible alternatives in this thread, which I am appreciative of.
I think that if nobody has strong feelings or issues with the current
implementation to add the sha1-unsafe test-tool, that we should do so
and take these patches.
In the future we can consider other things on top, like dropping the
test-sha1.sh script, having an unsafe pointer embedded within
the_hash_algo, or something else entirely. But those can be done on top,
or not at all, and I don't want to hold up this series for them.
Thanks,
Taylor
next prev parent reply other threads:[~2024-11-07 21:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 19:05 [PATCH v2 0/2] t/helper/test-tool: implement 'sha1-unsafe' helper Taylor Blau
2024-11-05 19:05 ` [PATCH v2 1/2] t/helper/test-sha1: prepare for an unsafe mode Taylor Blau
2024-11-06 1:38 ` Junio C Hamano
2024-11-07 0:48 ` brian m. carlson
2024-11-07 1:39 ` Jeff King
2024-11-07 1:49 ` brian m. carlson
2024-11-07 2:08 ` Jeff King
2024-11-07 3:08 ` Junio C Hamano
2024-11-07 21:30 ` Taylor Blau
2024-11-07 23:20 ` Taylor Blau
2024-11-08 17:26 ` Jeff King
2024-11-05 19:05 ` [PATCH v2 2/2] t/helper/test-tool: implement sha1-unsafe helper Taylor Blau
2024-11-07 1:47 ` [PATCH v2 0/2] t/helper/test-tool: implement 'sha1-unsafe' helper Jeff King
2024-11-07 2:05 ` brian m. carlson
2024-11-07 21:33 ` Taylor Blau
2024-11-08 17:23 ` Jeff King
2024-11-08 17:22 ` Jeff King
2024-11-07 21:36 ` Taylor Blau [this message]
2024-11-08 17:23 ` 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=Zy0yxDIgEmKtec/0@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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).