diff options
Diffstat (limited to 'src')
-rw-r--r-- | src/Makefile.am | 6 | ||||
-rw-r--r-- | src/copy.h | 8 | ||||
-rw-r--r-- | src/extract-magic | 6 | ||||
-rw-r--r-- | src/ls.c | 4 | ||||
-rw-r--r-- | src/pinky.c | 4 | ||||
-rw-r--r-- | src/pr.c | 12 | ||||
-rw-r--r-- | src/sort.c | 2 | ||||
-rw-r--r-- | src/split.c | 4 | ||||
-rw-r--r-- | src/timeout.c | 6 | ||||
-rw-r--r-- | src/who.c | 4 |
10 files changed, 28 insertions, 28 deletions
diff --git a/src/Makefile.am b/src/Makefile.am index db3159f7d..3f118181b 100644 --- a/src/Makefile.am +++ b/src/Makefile.am @@ -179,7 +179,7 @@ nodist_libver_a_SOURCES = version.c version.h AM_LDFLAGS = $(IGNORE_UNUSED_LIBRARIES_CFLAGS) # Sometimes, the expansion of $(LIBINTL) includes -lc which may -# include modules defining variables like `optind', so libcoreutils.a +# include modules defining variables like 'optind', so libcoreutils.a # must precede $(LIBINTL) in order to ensure we use GNU getopt. # But libcoreutils.a must also follow $(LIBINTL), since libintl uses # replacement functions defined in libcoreutils.a. @@ -458,8 +458,8 @@ uninstall-local: copy_sources = copy.c cp-hash.c extent-scan.c extent-scan.h -# Use `ginstall' in the definition of PROGRAMS and in dependencies to avoid -# confusion with the `install' target. The install rule transforms `ginstall' +# Use 'ginstall' in the definition of PROGRAMS and in dependencies to avoid +# confusion with the 'install' target. The install rule transforms 'ginstall' # to install before applying any user-specified name transformations. transform = s/ginstall/install/; $(program_transform_name) diff --git a/src/copy.h b/src/copy.h index a781820a8..715416e0f 100644 --- a/src/copy.h +++ b/src/copy.h @@ -189,8 +189,8 @@ struct cp_options propagates failure "out" to the caller, along with full diagnostics. If false, a failure to preserve file's security context does not change the invoking application's exit status, but may output diagnostics. - For example, with `cp --preserve=context` this flag is "true", - while with `cp --preserve=all` or `cp -a`, it is "false". */ + For example, with 'cp --preserve=context' this flag is "true", + while with 'cp --preserve=all' or 'cp -a', it is "false". */ bool require_preserve_context; /* If true, attempt to preserve extended attributes using libattr. @@ -202,8 +202,8 @@ struct cp_options propagates failure "out" to the caller, along with full diagnostics. If false, a failure to preserve file's extended attributes does not change the invoking application's exit status, but may output diagnostics. - For example, with `cp --preserve=xattr` this flag is "true", - while with `cp --preserve=all` or `cp -a`, it is "false". */ + For example, with 'cp --preserve=xattr' this flag is "true", + while with 'cp --preserve=all' or 'cp -a', it is "false". */ bool require_preserve_xattr; /* This allows us to output warnings in cases 2 and 4 below, diff --git a/src/extract-magic b/src/extract-magic index 0a30b0734..590f30d70 100644 --- a/src/extract-magic +++ b/src/extract-magic @@ -1,5 +1,5 @@ #!/usr/bin/perl -w -# Derive #define directives from specially formatted `case ...:' statements. +# Derive #define directives from specially formatted 'case ...:' statements. # Copyright (C) 2003, 2005, 2009-2012 Free Software Foundation, Inc. @@ -66,7 +66,7 @@ FIXME: describe OPTIONS: There are two modes of operation, the default, which is to emit - #define directives derived from specially formatted `case' statements, + #define directives derived from specially formatted 'case' statements, and that with --local, which is to emit a static inline function mapping S_MAGIC_* values to 1, 0, -1, corresponding to known-local, known-remote/distributed/network and unknown, respectively. @@ -109,7 +109,7 @@ EOF # case S_MAGIC_ROMFS: /* 0x7275 */ # emit one like this: # # define S_MAGIC_ROMFS 0x7275 - # Fail if there is a `case S_MAGIC_.*' line without + # Fail if there is a 'case S_MAGIC_.*' line without # a properly formed comment. my $map_comment = <<EOF; @@ -2910,7 +2910,7 @@ gobble_file (char const *name, enum filetype type, ino_t inode, f->stat_ok = true; - /* Note has_capability() adds around 30% runtime to `ls --color` */ + /* Note has_capability() adds around 30% runtime to 'ls --color' */ if ((type == normal || S_ISREG (f->stat.st_mode)) && print_with_color && is_colored (C_CAP)) f->has_capability = has_capability (absolute_name); @@ -3523,7 +3523,7 @@ print_current_files (void) } /* Replace the first %b with precomputed aligned month names. - Note on glibc-2.7 at least, this speeds up the whole `ls -lU` + Note on glibc-2.7 at least, this speeds up the whole 'ls -lU' process by around 17%, compared to letting strftime() handle the %b. */ static size_t diff --git a/src/pinky.c b/src/pinky.c index 4b4f3ed1a..57d87304c 100644 --- a/src/pinky.c +++ b/src/pinky.c @@ -179,10 +179,10 @@ time_string (const STRUCT_UTMP *utmp_ent) /* Don't take the address of UT_TIME_MEMBER directly. Ulrich Drepper wrote: - ``... GNU libc (and perhaps other libcs as well) have extended + "... GNU libc (and perhaps other libcs as well) have extended utmp file formats which do not use a simple time_t ut_time field. In glibc, ut_time is a macro which selects for backward compatibility - the tv_sec member of a struct timeval value.'' */ + the tv_sec member of a struct timeval value." */ time_t t = UT_TIME_MEMBER (utmp_ent); struct tm *tmp = localtime (&t); @@ -51,8 +51,8 @@ utilities, e.g. sort or cut. - Same as SunOS does. - With multicolumn output two conflicting POSIX requirements exist: - First 'default n-separator is TAB', second `output text columns shall - be of equal width'. Moreover POSIX specifies the number+separator a + First "default n-separator is TAB", second "output text columns shall + be of equal width". Moreover POSIX specifies the number+separator a part of the column, together with '-COLUMN' and '-a -COLUMN'. (With -m output the number shall occupy each line only once. Exactly the same situation as single column output exists.) @@ -72,9 +72,9 @@ PAGE_WIDTH may occur. The interference of the POSIX-compliant small letter options -w and -s: - ('interference' means `setting a _separator_ with -s switches off the + ("interference" means "setting a _separator_ with -s switches off the column structure and the default - not generally - page_width, - acts on -w option') + acts on -w option") options: text form / separator: equivalent new options: -w l -s[x] -------------------------------------------------------------------- @@ -216,8 +216,8 @@ is always printed with single column output only. The TAB-width varies with the TAB-position, e.g. with the left margin specified by -o option. - With multicolumn output priority is given to `equal width - of output columns' (a POSIX specification). The TAB-width + With multicolumn output priority is given to "equal width + of output columns" (a POSIX specification). The TAB-width is fixed to the value of the 1st column and does not change with different values of left margin. That means a fixed number of spaces is always printed in the place of diff --git a/src/sort.c b/src/sort.c index f38ded9c2..3cc1874cf 100644 --- a/src/sort.c +++ b/src/sort.c @@ -894,7 +894,7 @@ create_temp_file (int *pfd, bool survive_fd_exhaustion) Note this option was seen to shorten the runtime for sort on a multicore system with lots of RAM and other processes competing for CPU. It could be argued that more explicit - scheduling hints with `nice` et. al. are more appropriate + scheduling hints with 'nice' et. al. are more appropriate for this situation. POSIX_FADV_NOREUSE is a possibility as it could lower diff --git a/src/split.c b/src/split.c index 6032668f1..5fbce0ea2 100644 --- a/src/split.c +++ b/src/split.c @@ -774,7 +774,7 @@ ofile_open (of_t *files, size_t i_check, size_t nfiles) get an error, rather than waiting indefinitely. In specialised cases the consumer can keep reading from the fifo, terminating on conditions in the data - itself, or perhaps never in the case of `tail -f`. + itself, or perhaps never in the case of 'tail -f'. I.E. for fifos it is valid to attempt this reopen. We don't handle the filter_command case here, as create() @@ -1290,7 +1290,7 @@ main (int argc, char **argv) break; case type_rr: - /* Note, this is like `sed -n ${k}~${n}p` when k > 0, + /* Note, this is like 'sed -n ${k}~${n}p' when k > 0, but the functionality is provided for symmetry. */ lines_rr (k_units, n_units, buf, in_blk_size); break; diff --git a/src/timeout.c b/src/timeout.c index 8bb1da554..73367c429 100644 --- a/src/timeout.c +++ b/src/timeout.c @@ -32,8 +32,8 @@ If you start a command in the background, which reads from the tty and so is immediately sent SIGTTIN to stop, then the timeout process will ignore this so it can timeout the command as expected. - This can be seen with `timeout 10 dd&` for example. - However if one brings this group to the foreground with the `fg` + This can be seen with 'timeout 10 dd&' for example. + However if one brings this group to the foreground with the 'fg' command before the timer expires, the command will remain in the stop state as the shell doesn't send a SIGCONT because the timeout process (group leader) is already running. @@ -221,7 +221,7 @@ Mandatory arguments to long options are mandatory for short options too.\n\ -s, --signal=SIGNAL\n\ specify the signal to be sent on timeout.\n\ SIGNAL may be a name like 'HUP' or a number.\n\ - See `kill -l` for a list of signals\n"), stdout); + See 'kill -l' for a list of signals\n"), stdout); fputs (HELP_OPTION_DESCRIPTION, stdout); fputs (VERSION_OPTION_DESCRIPTION, stdout); @@ -218,10 +218,10 @@ time_string (const STRUCT_UTMP *utmp_ent) /* Don't take the address of UT_TIME_MEMBER directly. Ulrich Drepper wrote: - ``... GNU libc (and perhaps other libcs as well) have extended + "... GNU libc (and perhaps other libcs as well) have extended utmp file formats which do not use a simple time_t ut_time field. In glibc, ut_time is a macro which selects for backward compatibility - the tv_sec member of a struct timeval value.'' */ + the tv_sec member of a struct timeval value." */ time_t t = UT_TIME_MEMBER (utmp_ent); struct tm *tmp = localtime (&t); |