From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Randall Becker <randall.becker@nexbridge.ca>
Cc: "Randall S. Becker" <the.n.e.key@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
"Randall S . Becker" <rsbecker@nexbridge.com>
Subject: RE: [PATCH v2 1/2] Teach git version --build-options about libcurl
Date: Wed, 24 Jul 2024 12:51:31 +0200 (CEST) [thread overview]
Message-ID: <43ee3c5d-66be-dbda-542b-cf186e761c07@gmx.de> (raw)
In-Reply-To: <DS0PR17MB603115E943565C4281FBE199F4D42@DS0PR17MB6031.namprd17.prod.outlook.com>
Hi Randall,
On Mon, 24 Jun 2024, Randall Becker wrote:
> On Monday, June 24, 2024 10:13 AM, Johannes Schindelin wrote:
> >On Fri, 21 Jun 2024, Randall S. Becker wrote:
> >
> >> This change uses the libcurl LIBCURL_VERSION #define text macro. No
> >> stringification is required for the variable's use. If the #define is
> >> not present, that version is not reported.
> >>
> >> Signed-off-by: Randall S. Becker <rsbecker@nexbridge.com>
> >> ---
> >> help.c | 4 ++++
> >> 1 file changed, 4 insertions(+)
> >>
> >> diff --git a/help.c b/help.c
> >> index 1d057aa607..bf74e935b9 100644
> >> --- a/help.c
> >> +++ b/help.c
> >> @@ -1,4 +1,5 @@
> >> #include "git-compat-util.h"
> >> +#include "git-curl-compat.h" /* For LIBCURL_VERSION only */
> >> #include "config.h"
> >> #include "builtin.h"
> >> #include "exec-cmd.h"
> >> @@ -757,6 +758,9 @@ void get_version_info(struct strbuf *buf, int
> >> show_build_options)
> >>
> >> if (fsmonitor_ipc__is_supported())
> >> strbuf_addstr(buf, "feature: fsmonitor--daemon\n");
> >> +#if defined LIBCURL_VERSION
> >> + strbuf_addf(buf, "libcurl: %s\n", LIBCURL_VERSION);
> >
> >I am not sure that this is the most helpful information Git can provide:
> >It reports the version against which Git was _compiled_, whereas the version it is
> >_running against_ might be quite different.
> >
> >Wouldn't calling `curl_version()` make more sense here?
>
> I think the more important information is the build used.
It may be informative, but more informative would be what libcurl version
is actually used, not what was current at build time. There may
occasionally have been a mismatch between the build-time and the runtime
version that may have led to bugs, after all.
> My reasoning is that one can call run curl --version to see the current
> curl install.
That assumes quite a bit. It assumes that the libcurl that is used by the
`curl` executable is the same as the one that is used by
`git-remote-https`.
A very large chunk (by some recent internal measurement, roughly two
thirds) of the Git users use Windows, where this assumption would be
incorrect.
Ciao,
Johannes
next prev parent reply other threads:[~2024-07-24 10:51 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 [this message]
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
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=43ee3c5d-66be-dbda-542b-cf186e761c07@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=randall.becker@nexbridge.ca \
--cc=rsbecker@nexbridge.com \
--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 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).