From: Jeff King <peff@peff.net>
To: Anatoly Yakovenko <aeyakovenko@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: cant figure out how to get git working over https with a self signed certificate
Date: Sun, 17 Feb 2008 12:51:33 -0500 [thread overview]
Message-ID: <20080217175133.GA4655@coredump.intra.peff.net> (raw)
In-Reply-To: <e26d18e40802170948s4b769c5ej4d0fb01300fbad9a@mail.gmail.com>
On Sun, Feb 17, 2008 at 09:48:26AM -0800, Anatoly Yakovenko wrote:
> cant figure out how to get git working over https with a self signed
> certificate. I keep getting the dreaded "Error: no DAV locking
> support on remote repo"
Have you tried setting GIT_SSL_NO_VERIFY=1 in the environment? I haven't
tried http push, but the error message passing in this case for fetching
is not very good.
-Peff
prev parent reply other threads:[~2008-02-17 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 17:48 cant figure out how to get git working over https with a self signed certificate Anatoly Yakovenko
2008-02-17 17:51 ` Jeff King [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=20080217175133.GA4655@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=aeyakovenko@gmail.com \
--cc=git@vger.kernel.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).