If I have to make a guess, it may be a memory issue. Both devices you
mention has a very limited amount of RAM.
Maybe you should try git push --verbose, so Git will report a bit more
things to you.
On 18 Feb 2015 19:21, "Aaron Dennis" <akden...@gmail.com> wrote:
> As with WD, I am experiencing the same thing. Does anyone know the source
> of the error?
> With thanks,
> On Thursday, July 16, 2009 at 8:32:02 PM UTC-5, J wrote:
>> I'm encountering some strange behavior so I'm hoping someone can help
>> shed some light on this. When I do a git push, it ends with a "fatal:
>> The remote end hung up unexpectedly" but checking the git logs and the
>> remote repo seems to indicate the push went through fine. Rerunning
>> the git push returns "Everything is up to date".
>> So a little background, I have dropbear and git installed on a Palm
>> Pre and am trying to commit changes to a repo on gitorious. Since
>> dropbear is kind of screwy, I had to create a shell script (called
>> sssh) that does the equivalent of
>> ssh ~/.ssh/id_rsa $*
>> as dropbear will not automatically scan for the public key.
>> Additionally, I have defined GIT_SSH to be /opt/bin/sssh.
>> So at this point, everything seems to work (i.e. the push happens) but
>> I am not sure why the "fatal" message keeps popping up. Any ideas/
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.