From b13ba8b9b606c916e0bda39348ee009e920df22e Mon Sep 17 00:00:00 2001 From: giraffedata Date: Sat, 15 Jun 2019 17:51:35 +0000 Subject: Releaes 10.86.04 git-svn-id: http://svn.code.sf.net/p/netpbm/code/advanced@3632 9d0c8265-081b-0410-96cb-a4ca84ce46f8 --- doc/HISTORY | 7 +++++++ doc/INSTALL | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/HISTORY b/doc/HISTORY index 0cc8a44e..308f903b 100644 --- a/doc/HISTORY +++ b/doc/HISTORY @@ -4,6 +4,13 @@ Netpbm. CHANGE HISTORY -------------- +19.06.15 BJH Release 10.86.04 + + pamtris: Fix bug: debug trace left in + + pbmtozinc: Fix wrong output on big-endian machines. Broken in + Netpbm 10.71 (June 2015). + 19.05.04 BJH Release 10.86.03 pnmtopng: Fix bug: Defaults to no filters. Should be all diff --git a/doc/INSTALL b/doc/INSTALL index 39bbc0a5..aad0a5e5 100644 --- a/doc/INSTALL +++ b/doc/INSTALL @@ -126,7 +126,7 @@ Furthermore, as version information, the modification datetime of the source code is often more useful than the build datetime. For these reasons, it is possible to change this timestamping behavior by -setting the environment variable 'SOURCE_DATA_EPOCH'. That is supposed to be +setting the environment variable 'SOURCE_DATE_EPOCH'. That is supposed to be the POSIX datetime value (decimal number of seconds since 1969, excluding leap seconds) for when the source code was last modified. When you set this, before doing 'make' for the first time in a clean build tree, the resulting -- cgit 1.4.1