Hi Daniel,
thanks for your reply. "The tag in the git repo is the exact state of the files
when the release was generated".
Please verify this:
> git checkout libssh2-1.8.0
HEAD is now at 30e9c13... RELEASE-NOTES: adjusted for 1.8.0
>
> grep LIBSSH2_VERSION_MINOR include/libssh2.h
#define LIBSSH2_VERSION_MINOR 7
>
This is what i get after cloning the git repo
g...@github.com:libssh2/libssh2.git.
And this differs from what i can find in the same header file taken from the
1.8.0 tarball.
This is not what i expected and not something that i am used to from other
projects.
Just wanted to point you to this. Maybe i fooled myself somehow, but to me it
seems to be
inconsistent.
Cheers,
Afschin
On 11/2/18, 10:58 AM, "libssh2-devel on behalf of Daniel Stenberg"
<libssh2-devel-boun...@cool.haxx.se on behalf of dan...@haxx.se> wrote:
On Fri, 2 Nov 2018, Afschin Hormozdiary wrote:
> Could you please correct this version insonsistency or let me know if
this
> is intentionally?
The official libssh2 releases are the tarballs on the web page that also
are
attached to the release tags on github. The tarballs are also signed (by
me)
to allow everyone to verify their authenticity.
The tag in the git repo is the exact state of the files when the release
was
generated. It is consistent and reproducible.
--
/ daniel.haxx.se
_______________________________________________
libssh2-devel https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
_______________________________________________
libssh2-devel https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
