Hi, On Mon, 14 Jan 2008, [EMAIL PROTECTED] wrote:
> On Jan 14, 12:29 pm, Johannes Schindelin <[EMAIL PROTECTED]> > wrote: > > Could you be a bit more verbose with your bug report (i.e. a text copy > > of the failing output)? > > Not really, because that's all it says. (Is there any way to get more > verbose output?) > > I type: > > $ git pull > > nothing happens for a minute or two, and then the only output is: > > fatal: read error (Invalid Argument) Hmm, I never had that, yet. > A few other details: > > - I can delete the entire repository and then clone it again, and it > works fine. So there has been no change in firewall behaviour. > > - As mentioned, pull over HTTP appears to work fine. > > - If I try to 'git pull' (using git protocol) immediately after the > initial clone I get the expected 'Already up-to-date.' message. But > once there have been changes made, that I'm trying to pull, the > problems start. > > At this point I update over HTTP, which works. Then I try 'git pull' > again, but still the problem persists, and I get the same read error > as above. > > So after the clone it appears to work, but after any changes, even > with an up-to-date repository, it doesn't. > > Hope this gives you a few extra clues. :) Unfortunately not. I pull quite often (in fact, I fetch + rebase, but will try "pull" as a replacement soon), and it works. Could you try "git pull --rebase"? Ciao, Dscho
