Re: [libssh2] Wrap up a release!

2009-03-18 Thread Daniel Stenberg
On Tue, 17 Mar 2009, Dan Fandrich wrote: > In the spirit of being pedantic, names beginning with a single underscore > are supposed to be reserved for the OS and libraries. Although, since > libssh2 is a library that ships with lots of Linux-derived OSes, it could > probably fall under that loo

Re: mailing list administrativa

2009-03-18 Thread Daniel Stenberg
On Wed, 18 Mar 2009, Peter Stuge wrote: >> * I changed Reply-To: to point back to this list > > Not as cool. > http://woozle.org/~neale/papers/reply-to-still-harmful.html Yeah, I know this is religous and for each of the points in that document there are rebuttals in other documents you can also

Re: libssh2_sftp_init() blocks and does not return

2009-03-18 Thread Daniel Stenberg
On Wed, 18 Mar 2009, Heiner Steven wrote: Unfortunately it does not work: the program "hangs" in the library call libssh2_sftp_init() and does not return. Are you using a blocking or non-blocking socket? #0 0x7f6fe65790d5 in recv () from /lib/libc.so.6 #1 0x0042a62a in _libssh2

Re: mailing list administrativa

2009-03-18 Thread Peter Stuge
Daniel Stenberg wrote: > > http://woozle.org/~neale/papers/reply-to-still-harmful.html > > Yeah, I know this is religous and for each of the points in that > document there are rebuttals in other documents you can also easily > find with google. > > There's simply no "objective" best approach for

Re: mailing list administrativa

2009-03-18 Thread Peter Stuge
Daniel Stenberg wrote: > * It now completely discards posts from non-subscribers. Cool! > * I cut off the [libssh2] prefix from the subjects. Also cool! > * I changed Reply-To: to point back to this list Not as cool. http://woozle.org/~neale/papers/reply-to-still-harmful.html > since I g

Re: mailing list administrativa

2009-03-18 Thread Simon Josefsson
Daniel Stenberg writes: > On Wed, 18 Mar 2009, Peter Stuge wrote: > >>> * I changed Reply-To: to point back to this list >> >> Not as cool. >> http://woozle.org/~neale/papers/reply-to-still-harmful.html > > Yeah, I know this is religous and for each of the points in that document > there are reb

win32 patch for setting errno

2009-03-18 Thread E L
Here is a patch against libssh2-1.0.1-20090318.tar.gz that sets errno on windows by defining a wrapper _libssh2_recv and _libssh2_send. I was not sure where it should go, so I just put it in misc.c. Two other small changes: in two line libssh2_packet_read was not updated to _libsssh2_packet_read

[ libssh2-Bugs-1940276 ] Endlosloop in libssh2_sftp_close_handle

2009-03-18 Thread SourceForge.net
Bugs item #1940276, was opened at 2008-04-11 15:17 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=703942&aid=1940276&group_id=125852 Please note that this message will contain a full copy of the comment

[ libssh2-Bugs-2210282 ] libssh2 core dumps under AIX 5.3

2009-03-18 Thread SourceForge.net
Bugs item #2210282, was opened at 2008-10-30 19:26 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=703942&aid=2210282&group_id=125852 Please note that this message will contain a full copy of the comment

Re: libssh2_sftp_init() blocks and does not return

2009-03-18 Thread Keith Maika
Daniel Stenberg wrote: > On Wed, 18 Mar 2009, Heiner Steven wrote: > >> Unfortunately it does not work: the program "hangs" in the library >> call libssh2_sftp_init() and does not return. > > Are you using a blocking or non-blocking socket? > >> #0 0x7f6fe65790d5 in recv () from /lib/libc.

Re: win32 patch for setting errno

2009-03-18 Thread Peter Stuge
I mostly like it, but.. E L wrote: > +case WSAENOTCONN: > +case WSAECONNABORTED: > +errno = WSAENOTCONN; > +break; ..is it really wise to mix WSAE with E error codes? //Peter --

Re: win32 patch for setting errno

2009-03-18 Thread crc1021
Peter Stuge wrote: > I mostly like it, but.. > > E L wrote: > > +case WSAENOTCONN: > > +case WSAECONNABORTED: > > +errno = WSAENOTCONN; > > +break; > > ..is it really wise to mix WSAE with E error codes? > No. That was part of the code that I moved, but