From: "Aneesh Kumar" <aneesh.kumar@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: http git clone fails while ssh git clone works
Date: Thu, 3 Apr 2008 17:10:07 +0530 [thread overview]
Message-ID: <cc723f590804030440t14a8e4fdw77c4449dc2a4dbb8@mail.gmail.com> (raw)
git clone http://myhost...
ot 0bc8afe5e1f16a6c56bc677a6c85148455a474b3
got ee425b0b7fccd9cdea38ef781b76f034e0228391
error: Unable to find 31053805b6981918e1f39e7149f62d2a0068732a under
http://myhost.....
Cannot obtain needed commit 31053805b6981918e1f39e7149f62d2a0068732a
while processing commit 56933610fa9a36ea3fc053e02bd7442b55db85dd.
while git clone ssh://myhost... works fine.
The repo actually have the commit
git --git-dir=a.git show 31053805b6981918e1f39e7149f62d2a0068732a
shows the commit.
-aneesh
next reply other threads:[~2008-04-03 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 11:40 Aneesh Kumar [this message]
2008-04-03 12:51 ` http git clone fails while ssh git clone works Miklos Vajna
2008-04-03 14:52 ` Aneesh Kumar
2008-04-03 18:28 ` Mike Hommey
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=cc723f590804030440t14a8e4fdw77c4449dc2a4dbb8@mail.gmail.com \
--to=aneesh.kumar@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).