This is the mail archive of the
cygwin-cvs@cygwin.com
mailing list for the Cygwin project.
[newlib-cygwin] Use <filename> tag, not <pathname> tag
- From: Jon TURNEY <jturney at sourceware dot org>
- To: cygwin-cvs at sourceware dot org
- Date: 7 Jul 2016 13:48:58 -0000
- Subject: [newlib-cygwin] Use <filename> tag, not <pathname> tag
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=5ff2fcf9bd237558f6ce077baa6bb5ec9889992c
commit 5ff2fcf9bd237558f6ce077baa6bb5ec9889992c
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date: Sat Jul 2 16:46:48 2016 +0100
Use <filename> tag, not <pathname> tag
Fix an instance of the invalid <pathname> tag in Cygwin utils documentation,
by using the valid <filename> tag instead.
Signed-off-by: Jon Turney <jon.turney@dronecode.org.uk>
Diff:
---
winsup/doc/utils.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/winsup/doc/utils.xml b/winsup/doc/utils.xml
index 4853d92..12949c5 100644
--- a/winsup/doc/utils.xml
+++ b/winsup/doc/utils.xml
@@ -335,7 +335,7 @@ Other options:
However, the cygdrive prefix can be changed by the user, so symbolic links
created using the cygdrive prefix are not foolproof. With
<literal>-U</literal> cygpath will generate such paths prepended by the
- virtual <pathname>/proc/cygdrive</pathname> symbolic link, which will
+ virtual <filename>/proc/cygdrive</filename> symbolic link, which will
never change, so the created path is safe against changing the cygdrive
prefix.</para>