> Very interesting.
> What happens if you clone on the same host?
> $ cd /tmp/foo
> $ git clone /path/to/test
> or
> $ git clone file:///path/to/test
> ?
>
> If it fails, try looking at `git fsck`.
On the local side, git clone works and git fsck only indicate some
dandling blob and commits (that'
I looked at git's siurce recently because of the related problem. I was
looking at SmartHTTP protocol specific code and dont see in you message is
about git: or http: protocol, but it could be the same code in the back...
When a recent git client sends a pack file larger than 1mb it switches curl
On Oct 6, 1:11 pm, Simon Lipp wrote:
> > I'm not sure why later cloning the new repository fails, but I would
> > suggest using more sensible approach to putting the repository to
> > another machine in the first place:
[...]
> > $ git push --mirror foo
> Doesn’t change anything : on my local mac
Le Tue, 5 Oct 2010 11:51:37 -0700 (PDT),
Konstantin Khomoutov a écrit :
> I'm not sure why later cloning the new repository fails, but I would
> suggest using more sensible approach to putting the repository to
> another machine in the first place:
>
> $ ssh u...@host
> % mkdir ~/test.git && cd
maybe some script sit between git and the proxy, just strip off all
the "Expect" header?
is there such kind of utility program out of box?
Thanks,
On Oct 7, 12:22 am, James Fang wrote:
> our company provide internet access for us using proxy,
> but after configured http.proxy, i am keeping get H
our company provide internet access for us using proxy,
but after configured http.proxy, i am keeping get HTTP code 417
After a little google, i guess it's because the libcurl that git
use sent the "Expect: 100-continue" header, which the proxy(i guess a
Squid)
does not understand and reply with 4
