From 12e756e13c55c9e8c1923386b36319e3018c83c7 Mon Sep 17 00:00:00 2001 From: giraffedata Date: Wed, 2 Aug 2023 16:39:58 +0000 Subject: Fix wrong maxval with -lcmmaxval, failure to fail when maxvals are different an no options gives git-svn-id: http://svn.code.sf.net/p/netpbm/code/trunk@4569 9d0c8265-081b-0410-96cb-a4ca84ce46f8 --- doc/HISTORY | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'doc') diff --git a/doc/HISTORY b/doc/HISTORY index 35aeb6fe..5f849094 100644 --- a/doc/HISTORY +++ b/doc/HISTORY @@ -12,6 +12,12 @@ not yet BJH Release 11.04.00 "compiled by" value from --version common option. This helps with creating reproducible builds. + pamstack: fix bug: acts like -firstmaxval specified when it + wasn't. Introduced in Netpbm 11.03 (June 2023). + + pamstack: fix -lcmmaxval: chooses wrong maxval. Always + broken (-lcmmaxval was new in Netpbm 11.03 (June 2023)). + 23.06.28 BJH Release 11.03.00 pamstack: Add -firstmaxval, -lcmmaxval -- cgit 1.4.1