diff options
| author | Jim Meyering <meyering@fb.com> | 2015-04-27 08:19:47 -0700 |
|---|---|---|
| committer | Jim Meyering <meyering@fb.com> | 2015-05-01 18:09:51 -0700 |
| commit | 857ed5c3b95f5737020d57b30f202588fe023fde (patch) | |
| tree | 55d2a3af576a208980f5a95c451c1b25424a48ca | |
| parent | 312c75163a67986a4da33516b22e865aa3ca65ce (diff) | |
| download | sed-857ed5c3b95f5737020d57b30f202588fe023fde.tar.gz | |
maint: enable sc_file_system
* cfg.mk (local-checks-to-skip): Remove its exemption.
* BUGS (characters): s/filesystem/file system/
* ChangeLog-2014 (setup_jump): Likewise.
* doc/sed-in.texi: Likewise.
* doc/sed.texi: Likewise.
| -rw-r--r-- | BUGS | 2 | ||||
| -rw-r--r-- | ChangeLog-2014 | 2 | ||||
| -rw-r--r-- | cfg.mk | 1 | ||||
| -rw-r--r-- | doc/sed-in.texi | 2 | ||||
| -rw-r--r-- | doc/sed.texi | 2 |
5 files changed, 4 insertions, 5 deletions
@@ -76,7 +76,7 @@ regex syntax clashes (problems with backslashes) In short, `sed d -i' will let one delete the contents of a read-only file, and in general the `-i' option will let one clobber protected files. This is not a bug, but rather a - consequence of how the Unix filesystem works. + consequence of how the Unix file system works. The permissions on a file say what can happen to the data in that file, while the permissions on a directory say what can diff --git a/ChangeLog-2014 b/ChangeLog-2014 index a7a4270..9cc8dab 100644 --- a/ChangeLog-2014 +++ b/ChangeLog-2014 @@ -2564,7 +2564,7 @@ Sat May 30 04:02:29 PDT 1998 Ken Pizzini <ken@gnu.org> * configure.in: specify that config.h is to be derived from config_h.in in order to avoid the braindead - DOS filesystem limitations. + DOS file system limitations. Fri May 29 21:56:30 PDT 1998 Ken Pizzini <ken@gnu.org> @@ -26,7 +26,6 @@ local-checks-to-skip = \ sc_GPL_version \ sc_bindtextdomain \ sc_error_message_uppercase \ - sc_file_system \ sc_prohibit_atoi_atof \ sc_prohibit_magic_number_exit \ sc_prohibit_strcmp \ diff --git a/doc/sed-in.texi b/doc/sed-in.texi index 03f525f..0e10cde 100644 --- a/doc/sed-in.texi +++ b/doc/sed-in.texi @@ -2786,7 +2786,7 @@ In short, @samp{sed -i} will let you delete the contents of a read-only file, and in general the @option{-i} option (@pxref{Invoking sed, , Invocation}) lets you clobber protected files. This is not a bug, but rather a consequence -of how the Unix filesystem works. +of how the Unix file system works. The permissions on a file say what can happen to the data in that file, while the permissions on a directory say what can diff --git a/doc/sed.texi b/doc/sed.texi index 37c833c..fe07c48 100644 --- a/doc/sed.texi +++ b/doc/sed.texi @@ -2955,7 +2955,7 @@ In short, @samp{sed -i} will let you delete the contents of a read-only file, and in general the @option{-i} option (@pxref{Invoking sed, , Invocation}) lets you clobber protected files. This is not a bug, but rather a consequence -of how the Unix filesystem works. +of how the Unix file system works. The permissions on a file say what can happen to the data in that file, while the permissions on a directory say what can |