From: Reza Mahdi <admin@rzmahdi.ir>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git@vger.kernel.org, "Ramsay Jones" <ramsay@ramsayjones.plus.com>,
"Jeff King" <peff@peff.net>
Subject: Re: [PATCH v2] sha256: add support for Nettle
Date: Wed, 31 Aug 2022 10:04:31 +0430 [thread overview]
Message-ID: <a1a0672b-4f6b-debd-34d1-bbd9e60f520e@rzmahdi.ir> (raw)
In-Reply-To: <xmqqa69gr9ei.fsf@gitster.g>
On 7/11/2022 1:07 AM, Junio C Hamano wrote:
> (3) We can allow only one to be set and otherwise error out.
>
> If somebody wants to write autoconf support, they have to come
> up with the precedence order, or support the "--with[out]-X"
> thing to customize, in order to ensure that the configure
> script picks exactly one.
>
> Because not everybody has nor need to have enough knowledge to
> choose one among the multiple choices available to them, this
> is hostile to those who do not use configure.
>
> Not an improvement over what we have today.
I think this is the most used and familiar to folk. There is no need
to have multiple options since all of backends work perfectly.
And, of curse "--with-X" option must be meaningful when the sha256 is
enabled.
prev parent reply other threads:[~2022-08-31 5:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 23:05 [PATCH] sha256: add support for Nettle brian m. carlson
2022-07-06 1:00 ` Ramsay Jones
2022-07-06 1:08 ` brian m. carlson
2022-07-06 8:23 ` Jeff King
2022-07-06 8:45 ` Ævar Arnfjörð Bjarmason
2022-07-06 9:23 ` Jeff King
2022-07-06 10:39 ` brian m. carlson
2022-07-06 17:49 ` Junio C Hamano
2022-07-06 23:05 ` Junio C Hamano
2022-07-07 6:43 ` Junio C Hamano
2022-07-07 16:18 ` Junio C Hamano
2022-07-10 13:29 ` [PATCH v2] " brian m. carlson
2022-07-10 14:41 ` Ævar Arnfjörð Bjarmason
2022-07-10 16:39 ` Junio C Hamano
2022-07-10 20:12 ` brian m. carlson
2022-07-10 20:37 ` Junio C Hamano
2022-08-31 5:34 ` Reza Mahdi [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a1a0672b-4f6b-debd-34d1-bbd9e60f520e@rzmahdi.ir \
--to=admin@rzmahdi.ir \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=ramsay@ramsayjones.plus.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).