From: "Josh England" <jjengla@sandia.gov>
To: "Robin Rosenberg" <robin.rosenberg.lists@dewire.com>
Cc: git@vger.kernel.org
Subject: Re: git clone over http
Date: Tue, 04 Sep 2007 10:54:36 -0600 [thread overview]
Message-ID: <1188924876.6192.21.camel@beauty> (raw)
In-Reply-To: <200709021123.04218.robin.rosenberg.lists@dewire.com>
On Sun, 2007-09-02 at 11:23 +0200, Robin Rosenberg wrote:
> git clone (1.5.3) with http is somewhat unreliable. I've noticed if
> can actually give
> me different versions of a branch each time I run it, eventually yielding
> the one I'm expecting. And now this:
I don't see this behavior, but I do see other wierdness cloning via
http. Anytime I clone a repo (any repo) via http from behind the
firewall/proxy at work I never get any branches. 'git branch' only ever
shows 'master'. I can't checkout and work on any other branch. I can
work around the problem by cloning on a box that is more open, but was
wondering if anyone knows how to fix this.
-JE
next prev parent reply other threads:[~2007-09-04 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 9:23 git clone over http Robin Rosenberg
2007-09-02 18:54 ` Sean
2007-09-04 16:54 ` Josh England [this message]
2007-09-04 17:29 ` Junio C Hamano
2007-09-04 18:19 ` Robin Rosenberg
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=1188924876.6192.21.camel@beauty \
--to=jjengla@sandia.gov \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.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 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).