"Josh England" [off-list ref] writes:
On Sun, 2007-09-02 at 11:23 +0200, Robin Rosenberg wrote:
quoted
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?
tisdag 04 september 2007 skrev Junio C Hamano:
"Josh England" [off-list ref] writes:
quoted
On Sun, 2007-09-02 at 11:23 +0200, Robin Rosenberg wrote:
quoted
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?
The version where I noticed that strange behaviour was 1.5.3-rc6 on the client
and 1.5.1.4 on the server. The local repo was originally cloned with 1.5.something.
The interesting branch was a non-fastword one (i.e. "pu") and on the server I
was running git-update-server-info every 30 minutes. The pu branch on the server
was stable during the strange period. I'm not sure whether I got the odd behaviour
within those 30 minutes or not.
The url to the repo is http: //rosenberg.homelinux.net/repos/EGIT.git
I cannot http clone myself anymore it seems, but someone else may succeed better.
My curl is 7.16.0. Haven't tried any other version yet.
-- robin