From: Todd C. Miller <Todd.Miller@courtesan.com>
Date: Thu, 25 Aug 2016 19:24:03 +0000 (-0600)
Subject: Move SIGPIPE bug fix to 1.8.18 where it belongs
X-Git-Tag: SUDO_1_8_18^2~56
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c50b835255a50ec951287cd4944da1c69148fb18;p=sudo

Move SIGPIPE bug fix to 1.8.18 where it belongs
---

diff --git a/NEWS b/NEWS
index ae8aff0a8..692458223 100644
--- a/NEWS
+++ b/NEWS
@@ -39,14 +39,14 @@ What's new in Sudo 1.8.18
    have been added to control sudo's behavior when it is unable to
    write to the audit and I/O logs.
 
+ * Fixed a bug introduced in 1.8.17 where the SIGPIPE signal handler
+   was not being restored when sudo directly executes the command.
+
 What's new in Sudo 1.8.17p1
 
  * Fixed a bug introduced in 1.8.17 where the user's groups were
    not set on systems that don't use PAM.  Bug #749.
 
- * Fixed a bug introduced in 1.8.17 where the SIGPIPE signal handler
-   was not being restored when sudo directly executes the command.
-
 What's new in Sudo 1.8.17
 
  * On AIX, if /etc/security/login.cfg has auth_type set to PAM_AUTH