From: Junio C Hamano <gitster@pobox.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: Dmitry Smirnov <divis1969@gmail.com>, git@vger.kernel.org
Subject: Re: Git 1.7.5 problem with HTTPS
Date: Tue, 15 Nov 2011 15:10:56 -0800 [thread overview]
Message-ID: <7v1ut9uglb.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAJo=hJvdstr39suGMwxNoT+_cKThxsEYHi96eqja7HuHyPmhWA@mail.gmail.com> (Shawn Pearce's message of "Tue, 15 Nov 2011 07:03:52 -0800")
Shawn Pearce <spearce@spearce.org> writes:
> On Tue, Nov 15, 2011 at 05:52, Dmitry Smirnov <divis1969@gmail.com> wrote:
>
>> If I use the http URL (http://git.kernel.org/pub/scm/git/git.git) I
>> can clone with no problems.
>
> This may be a problem with the git.kernel.org HTTP server. It is
> probably not a problem with Git itself.
Not likely to be an issue with git.kernel.org either. I am puzzled.
$ git ls-remote https://git.kernel.org/pub/scm/git/git.git |
grep -e HEAD -e master
bc1bbe0c19a6ff39522b4fa3259f34150e308e1f HEAD
bc1bbe0c19a6ff39522b4fa3259f34150e308e1f refs/heads/master
$ rungit v1.7.5.4 ls-remote https://git.kernel.org/pub/scm/git/git.git |
grep -e HEAD -e master
bc1bbe0c19a6ff39522b4fa3259f34150e308e1f HEAD
bc1bbe0c19a6ff39522b4fa3259f34150e308e1f refs/heads/master
The only thing that immediately comes to mind is the rare smart-http
breakage in 1.7.5 but that was plugged in 1.7.5.1, so...
next prev parent reply other threads:[~2011-11-15 23:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 13:52 Git 1.7.5 problem with HTTPS Dmitry Smirnov
2011-11-15 15:03 ` Shawn Pearce
2011-11-15 23:10 ` Junio C Hamano [this message]
2011-11-16 7:11 ` Dmitry Smirnov
2011-11-16 7:18 ` Junio C Hamano
2011-11-16 7:34 ` Tay Ray Chuan
2011-11-16 8:51 ` Dmitry Smirnov
2011-11-16 9:13 ` Daniel Stenberg
2011-11-16 10:10 ` Dmitry Smirnov
2011-11-16 22:28 ` Jonathan Nieder
2011-11-16 7:04 ` Dmitry Smirnov
2011-11-16 10:32 ` Haitao Li
2011-11-17 6:36 ` Dmitry Smirnov
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=7v1ut9uglb.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=divis1969@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).