mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Marcin Wisnicki <>
To: git <>
Subject: Support SSL_CERT_DIR
Date: Tue, 20 Sep 2022 18:00:11 -0400	[thread overview]
Message-ID: <> (raw)

Is there any good reason why git ignores well established SSL_CERT_DIR
and uses only git-specific GIT_SSL_CAPATH?
Why not fallback to the standard variable if git one isn't set?
IMHO current behavior is bad UX.

Please CC, I'm not subscribed.

             reply	other threads:[~2022-09-20 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 22:00 Marcin Wisnicki [this message]
2022-09-21 21:26 ` Support SSL_CERT_DIR brian m. carlson

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \

* 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

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).