On 9 Nov 2005, at 12:09, Nick Hengeveld wrote:
quoted text
>
> Those curl result codes all look wrong, and sounds like a memory issue
> that Johannes Schindelin recently fixed in commit
> 90279074ca5cc336a8bfffd47d19d089b291b432.  Does your git build have  
> that
> patch?

I did not - I've pulled and rebuilt from master, and have that commit  
now.
It works better (not perfectly (there's a tags 403) but I suspect  
that may be permissions config at my server end or absence of tags in  
my repo or something mumble). I can do this a bunch of times in a row  
with the same results and the resulting cloned repository looks sane.

Ben

!535 [0] benc@piva:~/tmp/xa4$ cg clone http://www.hawaga.org.uk/ 
gitcompletion.git
defaulting to local storage area
20:46:16 URL:http://www.hawaga.org.uk/gitcompletion.git/HEAD [41/41] - 
 > "refs/heads/.origin-fetching" [1]
progress: 28 objects, 7901 bytes
http://www.hawaga.org.uk/gitcompletion.git/refs/tags/:
20:46:36 ERROR 403: Forbidden.

FINISHED --20:46:36--
Downloaded: 0 bytes in 0 files
New branch: a108bdc110dad770ec5c092759a8bc511790d21f
Cloned to gitcompletion/ (origin http://www.hawaga.org.uk/ 
gitcompletion.git available as branch "origin")


-- 
Ben ベン Бэн
http://www.hawaga.org.uk/ben/


-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html