coreutils/coreutils-basename_documentation.patch

Index: doc/coreutils.texi
===================================================================
--- doc/coreutils.texi.orig	2012-03-09 17:39:52.000000000 +0100
+++ doc/coreutils.texi	2012-03-09 17:54:51.848754123 +0100
@@ -12370,6 +12370,16 @@ This section describes commands that man
 @command{basename} removes any leading directory components from
 @var{name}.  Synopsis:
 
+@table @samp
+
+@item -z
+@itemx --zero
+@opindex -z
+@opindex --zero
+Separate output items with @sc{nul} characters.
+
+@end table
+
 @example
 basename @var{name} [@var{suffix}]
 @end example
- Update to 8.15: New programs realpath: print resolved file names. Bug fixes du --one-file-system (-x) would ignore any non-directory specified on the command line. For example, "touch f; du -x f" would print nothing. [bug introduced in coreutils-8.14] du -x no longer counts root directories of other file systems. [bug introduced in coreutils-5.1.0] ls --color many-entry-directory was uninterruptible for too long [bug introduced in coreutils-5.2.1] ls's -k option no longer affects how ls -l outputs file sizes. It now affects only the per-directory block counts written by -l, and the sizes written by -s. This is for compatibility with BSD and with POSIX 2008. Because -k is no longer equivalent to --block-size=1KiB, a new long option --kibibyte stands for -k. [bug introduced in coreutils-4.5.4] ls -l would leak a little memory (security context string) for each nonempty directory listed on the command line, when using SELinux. [bug probably introduced in coreutils-6.10 with SELinux support] split -n 1/2 FILE no longer fails when operating on a growing file, or (on some systems) when operating on a non-regular file like /dev/zero. It would report "/dev/zero: No such file or directory" even though the file obviously exists. Same for -n l/2. [bug introduced in coreutils-8.8, with the addition of the -n option] stat -f now recognizes the FhGFS and PipeFS file system types. tac no longer fails to handle two or more non-seekable inputs [bug introduced in coreutils-5.3.0] tail -f no longer tries to use inotify on GPFS or FhGFS file systems [you might say this was introduced in coreutils-7.5, along with inotify support, but the new magic numbers weren't in the usual places then.] ** Changes in behavior df avoids long UUID-including file system names in the default listing. With recent enough kernel/tools, these long names would be used, pushing second and subsequent columns far to the right. Now, when a long name refers to a symlink, and no file systems are specified, df prints the usually-short referent instead. tail -f now uses polling (not inotify) when any of its file arguments resides on a file system of unknown type. In addition, for each such argument, tail -f prints a warning with the FS type magic number and a request to report it to the bug-reporting address. - Bring german message catalog up to date. - Include upstream fix for du. - Include upstream patch fixing basename documentation. OBS-URL: https://build.opensuse.org/package/show/Base:System/coreutils?expand=0&rev=144 2012-03-09 19:02:35 +01:00			`Index: doc/coreutils.texi`
			`===================================================================`
			`--- doc/coreutils.texi.orig 2012-03-09 17:39:52.000000000 +0100`
			`+++ doc/coreutils.texi 2012-03-09 17:54:51.848754123 +0100`
			`@@ -12370,6 +12370,16 @@ This section describes commands that man`
			`@command{basename} removes any leading directory components from`
			`@var{name}. Synopsis:`

			`+@table @samp`
			`+`
			`+@item -z`
			`+@itemx --zero`
			`+@opindex -z`
			`+@opindex --zero`
			`+Separate output items with @sc{nul} characters.`
			`+`
			`+@end table`
			`+`
			`@example`
			`basename @var{name} [@var{suffix}]`
			`@end example`