From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Thomas Piekarski <t.piekarski@deloquencia.de>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>,
glperkins@lit.edu
Subject: Re: [PATCH] hier.7: Updating from FHS 2.3 to 3.0
Date: Tue, 19 May 2020 14:55:18 +0200 [thread overview]
Message-ID: <99ae2d82-e5a5-6511-a324-ee59da9642b3@gmail.com> (raw)
In-Reply-To: <9ebe073b-0e66-3ccd-a815-974eae0f9318@deloquencia.de>
>>> On second thought now I am not so sure about the way how this un-listing
>>> of /usr/X11R6 is mentioned in the patch.
>>>
>>> At the moment it is 'obsolete since FHS 3.0', we could write 'dropped
>>> since FHS 3.0' or 'not mentioned in FHS 3.0 anymore' instead.
>>>
>>> What do you think about such rephrasing? Or should it be just deleted
>>> from the manual page? How have been such updates (where something in
>>> documentation is silently not mentioned anymore) handled in the past?
>>
>> I think it would be sufficient to say something like "present in FHS
>> 2.3, removed in FHS 3.0".
>> Shall I make that change, or do you want to revise youe patch?
>
>
> That is a good idea.
>
> Being new to the process I would like to revise, make the change and
> update the patch.
Okay.
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-05-19 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 18:07 [PATCH] hier.7: Updating from FHS 2.3 to 3.0 Thomas Piekarski
2020-05-19 9:50 ` Michael Kerrisk (man-pages)
2020-05-19 12:24 ` Thomas Piekarski
2020-05-19 12:40 ` Michael Kerrisk (man-pages)
2020-05-19 12:53 ` Thomas Piekarski
2020-05-19 12:55 ` Michael Kerrisk (man-pages) [this message]
2020-05-19 15:34 ` [PATCH-v2] " Thomas Piekarski
2020-05-19 19:51 ` Michael Kerrisk (man-pages)
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=99ae2d82-e5a5-6511-a324-ee59da9642b3@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=glperkins@lit.edu \
--cc=linux-man@vger.kernel.org \
--cc=t.piekarski@deloquencia.de \
/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: link
Be 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 NNTP newsgroup(s).