"Josh England" <jjengla@xxxxxxxxxx> writes: > 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. Well, what does "git branch -r" say? If you see the remote tracking branches out of your branch (aka "heads/") namespace, that has been the default for quite some time since 1.5.0 days. Perhaps "more open" one has ancient git that dumped remote tracking branches in your branch namespace, while your "behind firewall" one has not so ancient git? - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
