From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Santos, Jose Renato G" <joserenato.santos@hp.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Git error when cloning pvops tree
Date: Mon, 09 Nov 2009 17:07:07 -0800 [thread overview]
Message-ID: <4AF8BCBB.5070601@goop.org> (raw)
In-Reply-To: <EF547E542C520A4D858CFEF5B404D0536080DFF272@GVW0673EXC.americas.hpqcorp.net>
On 11/09/09 16:35, Santos, Jose Renato G wrote:
> Thanks Jeremy
>
> It seems I might be out of luck
> Having HP IT support change company wide firewall policies seems an almost impossible task but I will try...
> I did a quick google search and it seems that others using http also experienced the same problem. However I could not find any solution except to use the git protocol (which is probably not an option for me)...
> Thanks for looking into it anyway
>
Don't get me wrong, http fetch for xen.git is something I intend to
support for precisely that reason. But I don't test it myself (unless
prodded), and it seems to magically break from time to time.
I can exactly reproduce your problem and I'm looking at a fix (or at
least workaround).
I'm wondering if a more stable long-term fix is to mirror git into hg to
enable http access, rather than rely on git's flaky http support.
J
next prev parent reply other threads:[~2009-11-10 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 23:44 Git error when cloning pvops tree Santos, Jose Renato G
2009-11-10 0:04 ` Jeremy Fitzhardinge
2009-11-10 0:35 ` Santos, Jose Renato G
2009-11-10 1:07 ` Jeremy Fitzhardinge [this message]
2009-11-10 1:10 ` Jeremy Fitzhardinge
2009-11-10 17:14 ` Santos, Jose Renato G
2009-11-10 2:24 ` Santos, Jose Renato G
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=4AF8BCBB.5070601@goop.org \
--to=jeremy@goop.org \
--cc=joserenato.santos@hp.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.