public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mtk.manpages at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug manual/16073] Improve the manual on symbolic links Date: Fri, 25 Oct 2013 21:54:00 -0000 [thread overview] Message-ID: <bug-16073-131-AAaWH4kSba@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16073-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16073 --- Comment #1 from Michael Kerrisk <mtk.manpages at gmail dot com> --- Fabrice, This is on a bit of a tangent, but from a man-pages perspective I agree. The man page used the same naming scheme, and the poor names were a nagging itch that I never quite scratched. Your bug report for the libc manual prompted me to change the man page, where I've used the names 'filepath' and 'linkpath'. I mildly prefer 'filepath' over 'target', but 'target' is not a bad name either. Cheers, Michael -- You are receiving this mail because: You are on the CC list for the bug.
next parent reply other threads:[~2013-10-25 21:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-16073-131@http.sourceware.org/bugzilla/> 2013-10-25 21:54 ` mtk.manpages at gmail dot com [this message] 2013-10-25 22:01 ` roland at gnu dot org 2013-10-26 8:26 ` libnoon at gmail dot com 2013-10-30 1:54 ` mtk.manpages at gmail dot com 2014-06-13 12:35 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-16073-131-AAaWH4kSba@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).