Make language less binary

2017-09-19 18:12:42 +00:00
parent fb04f2723a
commit 1e98b3b559
360 changed files with 502 additions and 502 deletions
--- a/tests/chage/15_chage-I_no_shadow_entry/config/etc/login.defs
+++ b/tests/chage/15_chage-I_no_shadow_entry/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/16_chage-m_no_shadow_entry/config/etc/login.defs
+++ b/tests/chage/16_chage-m_no_shadow_entry/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/17_chage-M_no_shadow_entry/config/etc/login.defs
+++ b/tests/chage/17_chage-M_no_shadow_entry/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/18_chage-d_no_shadow_entry/config/etc/login.defs
+++ b/tests/chage/18_chage-d_no_shadow_entry/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/19_chage-W_no_shadow_entry/config/etc/login.defs
+++ b/tests/chage/19_chage-W_no_shadow_entry/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/20_chage-E_no_shadow_entry/config/etc/login.defs
+++ b/tests/chage/20_chage-E_no_shadow_entry/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/25_chage_interractive/config/etc/login.defs
+++ b/tests/chage/25_chage_interractive/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/26_chage_interractive_date_0/config/etc/login.defs
+++ b/tests/chage/26_chage_interractive_date_0/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/27_chage_interractive_date_-1/config/etc/login.defs
+++ b/tests/chage/27_chage_interractive_date_-1/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/28_chage_interractive_date_EPOCH/config/etc/login.defs
+++ b/tests/chage/28_chage_interractive_date_EPOCH/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/29_chage_interractive_date_pre-EPOCH/config/etc/login.defs
+++ b/tests/chage/29_chage_interractive_date_pre-EPOCH/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/30_chage_interractive_date_pre-EPOCH2/config/etc/login.defs
+++ b/tests/chage/30_chage_interractive_date_pre-EPOCH2/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/31_chage_interractive_date_invalid/config/etc/login.defs
+++ b/tests/chage/31_chage_interractive_date_invalid/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/32_chage_interractive_date_invalid2/config/etc/login.defs
+++ b/tests/chage/32_chage_interractive_date_invalid2/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/33_chage_interractive-W_invalid1/config/etc/login.defs
+++ b/tests/chage/33_chage_interractive-W_invalid1/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/34_chage_interractive-W_invalid2/config/etc/login.defs
+++ b/tests/chage/34_chage_interractive-W_invalid2/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/35_chage_interractive-W-1/config/etc/login.defs
+++ b/tests/chage/35_chage_interractive-W-1/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/36_chage_interractive-I_invalid1/config/etc/login.defs
+++ b/tests/chage/36_chage_interractive-I_invalid1/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/37_chage_interractive-I_invalid2/config/etc/login.defs
+++ b/tests/chage/37_chage_interractive-I_invalid2/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/38_chage_interractive-I-1/config/etc/login.defs
+++ b/tests/chage/38_chage_interractive-I-1/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chage/39_chage_interractive-d-1/config/etc/login.defs
+++ b/tests/chage/39_chage_interractive-d-1/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chroot/chage/01_chage--root/config_chroot/etc/login.defs
+++ b/tests/chroot/chage/01_chage--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/chgpasswd/01_chgpasswd--root/config_chroot/etc/login.defs
+++ b/tests/chroot/chgpasswd/01_chgpasswd--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/chpasswd/01_chpasswd--root_nopam/config_chroot/etc/login.defs
+++ b/tests/chroot/chpasswd/01_chpasswd--root_nopam/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/chpasswd/02_chpasswd--root_pam/config_chroot/etc/login.defs
+++ b/tests/chroot/chpasswd/02_chpasswd--root_pam/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/chsh/01_chsh--root/config_chroot/etc/login.defs
+++ b/tests/chroot/chsh/01_chsh--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/gpasswd/01_gpasswd--root/config_chroot/etc/login.defs
+++ b/tests/chroot/gpasswd/01_gpasswd--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/groupadd/01_groupadd--root/config_chroot/etc/login.defs
+++ b/tests/chroot/groupadd/01_groupadd--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/groupdel/01_groupdel--root/config_chroot/etc/login.defs
+++ b/tests/chroot/groupdel/01_groupdel--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/groupmod/01_groupmod--root/config_chroot/etc/login.defs
+++ b/tests/chroot/groupmod/01_groupmod--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/grpck/01_grpck--root/config_chroot/etc/login.defs
+++ b/tests/chroot/grpck/01_grpck--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/grpconv/01_grpconv--root/config_chroot/etc/login.defs
+++ b/tests/chroot/grpconv/01_grpconv--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/grpunconv/01_grpunconv--root/config_chroot/etc/login.defs
+++ b/tests/chroot/grpunconv/01_grpunconv--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/lastlog/01_lastlog--root/config_chroot/etc/login.defs
+++ b/tests/chroot/lastlog/01_lastlog--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/login/01_login_sublogin/config/etc/login.defs
+++ b/tests/chroot/login/01_login_sublogin/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chroot/login/01_login_sublogin/config_chroot/etc/login.defs
+++ b/tests/chroot/login/01_login_sublogin/config_chroot/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/chroot/pwck/01_pwck--root/config_chroot/etc/login.defs
+++ b/tests/chroot/pwck/01_pwck--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/pwconv/01_pwconv--root/config_chroot/etc/login.defs
+++ b/tests/chroot/pwconv/01_pwconv--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/pwunconv/01_pwunconv--root/config_chroot/etc/login.defs
+++ b/tests/chroot/pwunconv/01_pwunconv--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/useradd/01_useradd--root/config_chroot/etc/login.defs
+++ b/tests/chroot/useradd/01_useradd--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/useradd/02_useradd--root_login.defs/config_chroot/etc/login.defs
+++ b/tests/chroot/useradd/02_useradd--root_login.defs/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/useradd/03_useradd--root_useradd.default/config_chroot/etc/login.defs
+++ b/tests/chroot/useradd/03_useradd--root_useradd.default/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/useradd/04_useradd--root_useradd-D/config_chroot/etc/login.defs
+++ b/tests/chroot/useradd/04_useradd--root_useradd-D/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/useradd/05_useradd--root_useradd-D-e-g/config_chroot/etc/login.defs
+++ b/tests/chroot/useradd/05_useradd--root_useradd-D-e-g/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/userdel/01_userdel--root/config_chroot/etc/login.defs
+++ b/tests/chroot/userdel/01_userdel--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/chroot/usermod/01_usermod--root/config_chroot/etc/login.defs
+++ b/tests/chroot/usermod/01_usermod--root/config_chroot/etc/login.defs
@@ -136,7 +136,7 @@ TTYPERM		0600
 # useradd and newusers to set the mode of the new home directories.
 # 022 is the "historical" value in Debian for UMASK
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #
 # Prefix these values with "0" to get octal, "0x" to get hexadecimal.
--- a/tests/crypt/login.defs_DES-MD5_CRYPT_ENAB/config/etc/login.defs
+++ b/tests/crypt/login.defs_DES-MD5_CRYPT_ENAB/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/crypt/login.defs_DES/config/etc/login.defs
+++ b/tests/crypt/login.defs_DES/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/crypt/login.defs_MD5/config/etc/login.defs
+++ b/tests/crypt/login.defs_MD5/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/crypt/login.defs_MD5_CRYPT_ENAB/config/etc/login.defs
+++ b/tests/crypt/login.defs_MD5_CRYPT_ENAB/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/crypt/login.defs_SHA256-round-max/config/etc/login.defs
+++ b/tests/crypt/login.defs_SHA256-round-max/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/crypt/login.defs_SHA256-round-min-max/config/etc/login.defs
+++ b/tests/crypt/login.defs_SHA256-round-min-max/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/crypt/login.defs_SHA256-round-min/config/etc/login.defs
+++ b/tests/crypt/login.defs_SHA256-round-min/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/crypt/login.defs_SHA256/config/etc/login.defs
+++ b/tests/crypt/login.defs_SHA256/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/crypt/login.defs_SHA512/config/etc/login.defs
+++ b/tests/crypt/login.defs_SHA512/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/crypt/login.defs_none/config/etc/login.defs
+++ b/tests/crypt/login.defs_none/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chage/01_chage_openRW_passwd_failure/config/etc/login.defs
+++ b/tests/failures/chage/01_chage_openRW_passwd_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chage/02_chage_openRO_passwd_failure/config/etc/login.defs
+++ b/tests/failures/chage/02_chage_openRO_passwd_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chage/03_chage_openRW_shadow_failure/config/etc/login.defs
+++ b/tests/failures/chage/03_chage_openRW_shadow_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chage/04_chage_openRO_shadow_failure/config/etc/login.defs
+++ b/tests/failures/chage/04_chage_openRO_shadow_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chage/05_chage_rename_shadow_failure/config/etc/login.defs
+++ b/tests/failures/chage/05_chage_rename_shadow_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chage/06_chage_rename_passwd_failure/config/etc/login.defs
+++ b/tests/failures/chage/06_chage_rename_passwd_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chgpasswd/01_chgpasswd-e_open_group_failure/config/etc/login.defs
+++ b/tests/failures/chgpasswd/01_chgpasswd-e_open_group_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chgpasswd/02_chgpasswd-e_open_gshadow_failure/config/etc/login.defs
+++ b/tests/failures/chgpasswd/02_chgpasswd-e_open_gshadow_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chgpasswd/03_chgpasswd-e_rename_group_failure/config/etc/login.defs
+++ b/tests/failures/chgpasswd/03_chgpasswd-e_rename_group_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chgpasswd/04_chgpasswd-e_rename_gshadow_failure/config/etc/login.defs
+++ b/tests/failures/chgpasswd/04_chgpasswd-e_rename_gshadow_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chpasswd-PAM/01_chpasswd-e_open_passwd_failure/config/etc/login.defs
+++ b/tests/failures/chpasswd-PAM/01_chpasswd-e_open_passwd_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chpasswd-PAM/02_chpasswd-e_open_shadow_failure/config/etc/login.defs
+++ b/tests/failures/chpasswd-PAM/02_chpasswd-e_open_shadow_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chpasswd-PAM/03_chpasswd-e_rename_passwd_failure/config/etc/login.defs
+++ b/tests/failures/chpasswd-PAM/03_chpasswd-e_rename_passwd_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chpasswd-PAM/04_chpasswd-e_rename_shadow_failure/config/etc/login.defs
+++ b/tests/failures/chpasswd-PAM/04_chpasswd-e_rename_shadow_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chsh/01_chsh_open_passwd_failure/config/etc/login.defs
+++ b/tests/failures/chsh/01_chsh_open_passwd_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/chsh/02_chsh_rename_passwd_failure/config/etc/login.defs
+++ b/tests/failures/chsh/02_chsh_rename_passwd_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/cppw/01_cppw_open_passwd_in_failure/config/etc/login.defs
+++ b/tests/failures/cppw/01_cppw_open_passwd_in_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/cppw/02_cppw_open_passwd_backup_failure/config/etc/login.defs
+++ b/tests/failures/cppw/02_cppw_open_passwd_backup_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/cppw/03_cppw_rename_passwd_failure/config/etc/login.defs
+++ b/tests/failures/cppw/03_cppw_rename_passwd_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/gpasswd/01_gpasswd_group_open_failure/config/etc/login.defs
+++ b/tests/failures/gpasswd/01_gpasswd_group_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/gpasswd/02_gpasswd_gshadow_open_failure/config/etc/login.defs
+++ b/tests/failures/gpasswd/02_gpasswd_gshadow_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/gpasswd/03_gpasswd-a_group_open_failure/config/etc/login.defs
+++ b/tests/failures/gpasswd/03_gpasswd-a_group_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/gpasswd/04_gpasswd-d_group_open_failure/config/etc/login.defs
+++ b/tests/failures/gpasswd/04_gpasswd-d_group_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/gpasswd/05_gpasswd-r_group_open_failure/config/etc/login.defs
+++ b/tests/failures/gpasswd/05_gpasswd-r_group_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/gpasswd/06_gpasswd-R_gshadow_open_failure/config/etc/login.defs
+++ b/tests/failures/gpasswd/06_gpasswd-R_gshadow_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/gpasswd/07_gpasswd-A_gshadow_open_failure/config/etc/login.defs
+++ b/tests/failures/gpasswd/07_gpasswd-A_gshadow_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/gpasswd/08_gpasswd_group_openRO_failure/config/etc/login.defs
+++ b/tests/failures/gpasswd/08_gpasswd_group_openRO_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/gpasswd/09_gpasswd_gshadow_openRO_failure/config/etc/login.defs
+++ b/tests/failures/gpasswd/09_gpasswd_gshadow_openRO_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/gpasswd/10_gpasswd_group_rename_failure/config/etc/login.defs
+++ b/tests/failures/gpasswd/10_gpasswd_group_rename_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/gpasswd/11_gpasswd_gshadow_rename_failure/config/etc/login.defs
+++ b/tests/failures/gpasswd/11_gpasswd_gshadow_rename_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupadd/01_groupadd_gshadow_rename_failure/config/etc/login.defs
+++ b/tests/failures/groupadd/01_groupadd_gshadow_rename_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupadd/02_groupadd_group_rename_failure/config/etc/login.defs
+++ b/tests/failures/groupadd/02_groupadd_group_rename_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupadd/03_groupadd_gshadow_open_failure/config/etc/login.defs
+++ b/tests/failures/groupadd/03_groupadd_gshadow_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupadd/04_groupadd_group_open_failure/config/etc/login.defs
+++ b/tests/failures/groupadd/04_groupadd_group_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupdel/01_groupdel_gshadow_rename_failure/config/etc/login.defs
+++ b/tests/failures/groupdel/01_groupdel_gshadow_rename_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupdel/02_groupdel_group_rename_failure/config/etc/login.defs
+++ b/tests/failures/groupdel/02_groupdel_group_rename_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupdel/03_groupdel_gshadow_open_failure/config/etc/login.defs
+++ b/tests/failures/groupdel/03_groupdel_gshadow_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupdel/04_groupdel_group_open_failure/config/etc/login.defs
+++ b/tests/failures/groupdel/04_groupdel_group_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupmod/01_groupmod_change_group_name_gshadow_rename_failure/config/etc/login.defs
+++ b/tests/failures/groupmod/01_groupmod_change_group_name_gshadow_rename_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupmod/02_groupmod_change_gid_change_primary_group_passwd_rename_failure/config/etc/login.defs
+++ b/tests/failures/groupmod/02_groupmod_change_gid_change_primary_group_passwd_rename_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupmod/03_groupmod_change_group_name_group_rename_failure/config/etc/login.defs
+++ b/tests/failures/groupmod/03_groupmod_change_group_name_group_rename_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupmod/04_groupmod_group_open_failure/config/etc/login.defs
+++ b/tests/failures/groupmod/04_groupmod_group_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupmod/05_groupmod_gshadow_open_failure/config/etc/login.defs
+++ b/tests/failures/groupmod/05_groupmod_gshadow_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/tests/failures/groupmod/06_groupmod_-g_no_gshadow_open_failure/config/etc/login.defs
+++ b/tests/failures/groupmod/06_groupmod_-g_no_gshadow_open_failure/config/etc/login.defs
@@ -156,7 +156,7 @@ ERASECHAR	0177
 KILLCHAR	025
 # 022 is the "historical" value in Debian for UMASK when it was used
 # 027, or even 077, could be considered better for privacy
-# There is no One True Answer here : each sysadmin must make up his/her
+# There is no One True Answer here : each sysadmin must make up their
 # mind.
 #UMASK		022

--- a/Show More
+++ b/Show More