From: <rsbecker@nexbridge.com>
To: "'Jeff King'" <peff@peff.net>
Cc: "'Dragan Simic'" <dsimic@manjaro.org>,
"'Christian Couder'" <christian.couder@gmail.com>,
<git@vger.kernel.org>, "'Junio C Hamano'" <gitster@pobox.com>,
"'Patrick Steinhardt'" <ps@pks.im>,
"'John Cai'" <johncai86@gmail.com>,
"'Johannes Schindelin'" <Johannes.Schindelin@gmx.de>
Subject: RE: [PATCH 0/3] Advertise OS version
Date: Wed, 19 Jun 2024 10:57:38 -0400 [thread overview]
Message-ID: <000701dac259$0a768bb0$1f63a310$@nexbridge.com> (raw)
In-Reply-To: <20240619145246.GB957055@coredump.intra.peff.net>
On Wednesday, June 19, 2024 10:53 AM, Peff wrote:
>On Wed, Jun 19, 2024 at 10:41:54AM -0400, rsbecker@nexbridge.com wrote:
>
>> >A configuration knob that would allow it to be disabled entirely, or
>> >be enabled with more details to be sent would also be fine with me.
>>
>> While in the code, can I suggest including the OpenSSL version used in
>> the build? This came up in at a customer a few weeks ago and they
>> could not answer the question of what git build they were using.
>> Turned out it used the wrong OpenSSL header compared to what they had
>> installed.
>
>At the point you are dealing one-on-one with somebody, I don't think protocol-level
>messages like this are the best spot for debugging. But it might make sense to teach
>"git version --build-options" to report the openssl version.
Much better idea. Will look into it. Thanks.
next prev parent reply other threads:[~2024-06-19 14:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 12:57 [PATCH 0/3] Advertise OS version Christian Couder
2024-06-19 12:57 ` [PATCH 1/3] version: refactor strbuf_sanitize() Christian Couder
2024-06-19 18:40 ` Eric Sunshine
2024-06-19 12:57 ` [PATCH 2/3] version: refactor get_uname_info() Christian Couder
2024-06-19 12:57 ` [PATCH 3/3] connect: advertise OS version Christian Couder
2024-06-19 13:18 ` [PATCH 0/3] Advertise " Dragan Simic
2024-06-19 13:45 ` Jeff King
2024-06-19 13:50 ` Dragan Simic
2024-06-19 14:01 ` Christian Couder
2024-06-19 14:19 ` Dragan Simic
2024-06-19 14:41 ` rsbecker
2024-06-19 14:52 ` Jeff King
2024-06-19 14:57 ` rsbecker [this message]
2024-06-19 15:53 ` Dragan Simic
2024-06-19 14:50 ` Jeff King
2024-06-19 15:25 ` rsbecker
2024-06-19 22:46 ` brian m. carlson
2024-06-20 15:25 ` Jeff King
2024-06-20 16:28 ` Junio C Hamano
2024-12-09 16:14 ` Usman Akinyemi
2024-12-09 16:34 ` rsbecker
2024-12-10 18:51 ` Usman Akinyemi
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='000701dac259$0a768bb0$1f63a310$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=dsimic@manjaro.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johncai86@gmail.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
/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.