Has anyone seen this before? It only happens to me with git version
1.7.9.5 on a ubuntu x86_64 machine.
Thanks
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To view this discussion on the web visit
It's two of us... In git version 1.7.9.5 the error has moved to line 1140.
I can't believe nothing happened on this thread since back in 2009!
We're either both probably doing something very wrong, or noone is using
git send-email on ubuntu...
sâmbătă, 14 martie 2009, 22:59:01 UTC+2, Frew a
All looks OK below, but I do get that same message myself when there's a
connection problem. Looks like you're using ssh, and it's there where I'd
look first. Can you successfully transfer a large file over ssh to the
server named 'git' using the 'git' account? Try this:
$ scp large-file.dat
Maybe I can also help shed some light here.
I'll start with the difference between patch and commit. Patch is --
simply put -- a diff between two versions of the same tree. You can only
apply the patch to the same version of the tree from which it was
generated. Period.
In comes git to add a
I could actively tell git that two trees are the same.
I'll keep my eyes open for an answer to this one on this list, as this
interests me as much as it does you. This is key for your problem.
But I can tell you this much: over here, where I'm working, we cloned
entire reposes -- history and all
Referring specifically to your error, it's caused by the fact that the
linker doesn't find libz.a in the proper place for libs, e.g. /usr/lib or
/usr/local/lib
And that's most likely because you don't have zlib installed in your system.
--
You received this message because you are subscribed
Indeed, the logs you posted don't tell me much. Indeed, it appears as if
the ssh client closes the connection and sends an error code upstream,
probably because the server doesn't ack the close (I'm speculating...).
Maybe the following questions need also be answered before trying anything
Yeah, I'd definitely do that, especially since it should be as easy as
moving .vmx files between physical machines that are already connected. I'd
not rely upon the wm-switches for anything more complex than ftp-ing
between VMs... I fear they were not even tested for doing more than just