Thanks for doing all the leg work on this, it is appreciated. As time allows I will be committing some of the updates we've made over the years, but I was wondering what to do about commits that break binary compatibility. Should we (you?) create a 1.6 branch to commit bigger changes to? For example, the known hosts error values I submitted yesterday could live there. Furthermore, I have sha256 kex support but is also binary incompatible.
Thoughts? Will > On Mar 12, 2015, at 3:39 AM, Daniel Stenberg <dan...@haxx.se> wrote: > > Hi! > > I just wanted to point out to everyone, especially if you're not used to > working with projects on github, that you may want to click "watch" or at > least "star" the libssh2 source code repo: > > https://github.com/libssh2/libssh2 > > Doing so will get you notified when things happen there. Like new pull > requests etc. > > -- > > / daniel.haxx.se > _______________________________________________ > libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
