From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>,
"'Randall Becker'" <randall.becker@nexbridge.ca>
Cc: "'Johannes Schindelin'" <Johannes.Schindelin@gmx.de>,
"'Randall S. Becker'" <the.n.e.key@gmail.com>,
<git@vger.kernel.org>
Subject: RE: [PATCH v2 2/2] Teach git version --build-options about zlib versions.
Date: Wed, 24 Jul 2024 12:33:35 -0400 [thread overview]
Message-ID: <051501dadde7$3ea474c0$bbed5e40$@nexbridge.com> (raw)
In-Reply-To: <xmqqed7iyd4i.fsf@gitster.g>
On July 24, 2024 12:22 PM, Junio C Hamano wrote:
>Randall Becker <randall.becker@nexbridge.ca> writes:
>
>> What I actually proposed was splitting --build-options with runtime
>> (some representative argument). This would allow the headers used at
>> build time (--build-options) to be reported *and* the runtime
>> (probably) DLL versions (but would also report static linked library
>> versions) to be reported. Both are useful from a support standpoint.
>
>That certainly is a reasonable future plan.
>
>> However, the --build-options argument was intended to report an
>> invariant set of values used during the build, so I would rather not
>> conflate the two distinctly different semantic values.
>
>This reasoning makes sense to me, too.
>
>Please wrap overly long lines to reasonable width, by the way.
Sorry about that. Outlook is a pain in that regard, and different recipients
define different line lengths.
I will do my best in future for git.
--Randall
prev parent reply other threads:[~2024-07-24 16:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 18:09 [PATCH v2 0/2] Teach git version --build-options about zlib+libcurl Randall S. Becker
2024-06-21 18:09 ` [PATCH v2 1/2] Teach git version --build-options about libcurl Randall S. Becker
2024-06-24 14:13 ` Johannes Schindelin
2024-06-24 14:33 ` Randall Becker
2024-06-24 17:08 ` Dragan Simic
2024-06-24 21:15 ` rsbecker
2024-06-24 21:52 ` Dragan Simic
2024-06-24 21:56 ` Randall Becker
2024-07-24 10:51 ` Johannes Schindelin
2024-06-24 15:29 ` Jeff King
2024-06-24 16:06 ` Junio C Hamano
2024-06-24 23:55 ` Jeff King
2024-06-25 0:00 ` Junio C Hamano
2024-07-24 10:48 ` Johannes Schindelin
2024-07-24 20:55 ` Jeff King
2024-07-24 22:17 ` Johannes Schindelin
2024-07-25 6:52 ` Jeff King
2024-07-25 15:28 ` Junio C Hamano
2024-07-26 0:41 ` Jeff King
2024-06-21 18:09 ` [PATCH v2 2/2] Teach git version --build-options about zlib versions Randall S. Becker
2024-06-24 14:15 ` Johannes Schindelin
2024-06-24 14:38 ` Randall Becker
2024-07-24 11:02 ` Johannes Schindelin
2024-07-24 13:36 ` Randall Becker
2024-07-24 16:21 ` Junio C Hamano
2024-07-24 16:33 ` rsbecker [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='051501dadde7$3ea474c0$bbed5e40$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=randall.becker@nexbridge.ca \
--cc=the.n.e.key@gmail.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.