From: David Woodhouse <dwmw2@infradead.org>
To: Laurent Pinchart <laurent.pinchart@technotrade.biz>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Problem cloning Linus' GIT tree!
Date: Sat, 21 Apr 2007 20:23:05 +0100 [thread overview]
Message-ID: <1177183385.2854.39.camel@pmac.infradead.org> (raw)
In-Reply-To: <200704171532.00215.laurent.pinchart@technotrade.biz>
On Tue, 2007-04-17 at 15:31 +0200, Laurent Pinchart wrote:
> I'm not sure about that. The http repository is not broken, it's just
> stripped. The http:// protocol handler in git might need to be fixed.
The http:// protocol handler is rarely going to work properly. If your
firewall is broken, I would suggest just fixing it.
--
dwmw2
prev parent reply other threads:[~2007-04-21 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 10:42 Problem cloning Linus' GIT tree! Gerald Ruescher
2007-04-17 10:28 ` Laurent Pinchart
2007-04-17 14:09 ` Gerald Ruescher
2007-04-17 13:31 ` Laurent Pinchart
2007-04-21 19:23 ` David Woodhouse [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=1177183385.2854.39.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=laurent.pinchart@technotrade.biz \
--cc=linuxppc-embedded@ozlabs.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).