From: "Philip Oakley" <philipoakley@iee.org>
To: "'joe'" <joezeve@openmailbox.org>, <git@vger.kernel.org>
Cc: <git-for-windows@googlegroups.com>
Subject: RE: incorrect ssl directory set on git-scm
Date: Sat, 26 Dec 2015 18:31:15 -0000 [thread overview]
Message-ID: <000401d1400b$9b322df0$d19689d0$@iee.org> (raw)
In-Reply-To: <loom.20151226T143541-907@post.gmane.org>
> From Jo zeve
>
> git-scm comes with ca-bundle.trust.crt and cert.pem, it currently (2.6.4)
> assumes that they are stored in
>
> <dir name>\mingw32\libexec\ssl\certs
> <dir name>\mingw32\libexec\ssl
>
> which is not true, they are in
>
> <dir name>\mingw32\ssl\certs
> <dir name>\mingw32\ssl
>
The location of the CA certs is discussed in
https://github.com/git-for-windows/git/issues/425 among others (do have a
search through the issues for the other discussions).
As I understand it from watching the discussions go by, Windows and *nix
have different perspectives on where they should be stored.
If you can help with a suitable patch / Pull request that would be great.
Especially as it looks like you desire the 32 bitness version.
--
Philip
prev parent reply other threads:[~2015-12-26 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 13:35 bug: incorrect ssl directory set on git-scm joe
2015-12-26 18:31 ` Philip Oakley [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='000401d1400b$9b322df0$d19689d0$@iee.org' \
--to=philipoakley@iee.org \
--cc=git-for-windows@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=joezeve@openmailbox.org \
/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).