Discussion:
spiped 1.3.1 released
Colin Percival
2013-04-13 07:50:28 UTC
Permalink
Hi all,

I have just tagged the spiped-1.3.1 source tree and uploaded the release
tarball to the http://www.tarsnap.com/spiped.html . The SHA256 hash of
the release tarball is
8a58a983be460b88ed5a105201a0f0afacb83382208761837a62871dcca42fee

This is the same as spiped-1.3.0 with the exception of adding a missing
<stdint.h> inclusion in one C file and a couple of minor code cleanups
which improve clarity while not changing the code meaning.

- --
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
James Turner
2013-04-13 19:38:46 UTC
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I have just tagged the spiped-1.3.1 source tree and uploaded the release
tarball to the http://www.tarsnap.com/spiped.html . The SHA256 hash of
the release tarball is
8a58a983be460b88ed5a105201a0f0afacb83382208761837a62871dcca42fee
This is the same as spiped-1.3.0 with the exception of adding a missing
<stdint.h> inclusion in one C file and a couple of minor code cleanups
which improve clarity while not changing the code meaning.
- --
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
iEYEARECAAYFAlFpDkQACgkQOM7KaQxqam6EvwCfZVJuLKLCZHNLS0XVAVoZ+ejI
FQQAnRzN7SdYKofNdEBf8d9TkyA4Im9e
=tQNM
-----END PGP SIGNATURE-----
OpenBSD didn't seem to need the missing include but I updated our port
nonetheless.
--
James Turner
Colin Percival
2013-04-13 19:52:07 UTC
Permalink
Post by Colin Percival
This is the same as spiped-1.3.0 with the exception of adding a missing
<stdint.h> inclusion in one C file and a couple of minor code cleanups
which improve clarity while not changing the code meaning.
OpenBSD didn't seem to need the missing include but I updated our port
nonetheless.
I think all the BSDs have uintX_t namespace pollution in headers where
POSIX does not require that they be defined -- it's convenient right up
to the point where you want to run code on different platforms after
originally writing it on BSD...
--
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
Loading...