From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Elie De Brauwer <eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Michael Kerrisk-manpages
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] wavelan.4: Remove manpage for no longer available driver
Date: Thu, 05 Sep 2013 10:04:57 +0200 [thread overview]
Message-ID: <52283B29.4030102@gmail.com> (raw)
In-Reply-To: <CAGWqfihQ6mjrygiy0Ytopx5yYfU4C7Cj6=byBH09PMXCfivAAQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 04.09.2013 21:13, Elie De Brauwer wrote:
> On Wed, Sep 4, 2013 at 2:38 PM, Michael Kerrisk (man-pages)
> <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> Hello Elie,
>>
>> On Sat, Aug 31, 2013 at 8:13 AM, Elie De Brauwer
>> <eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>> Hello Michael, list,
>>>
>>> The current release of the manpages contains wavelan(4), but support for
>>> this module/driver is gone since several years. Starting from 2.6.32
>>> (2009 )the driver was put in a staging mode ready for deprecation:
>>>
>>> The announcement e-mail is here: http://lwn.net/Articles/367876/
>>> Then it lived in staging for two more releases with the following cry
>>> for help: http://lxr.linux.no/linux+v2.6.34.14/drivers/staging/wavelan/TODO
>>> and disappeared since 2.6.35 and then all other traces (documentation, etc)
>>> were also removed.
>>>
>>> Hence I think it's pointless to continue dragging this information around,
>>> if the driver doesn't have much use to people anymore, I doubt the manpage
>>> has.
>>
>> I'm reluctant to discard the page outright (occasionally, people do
>> want to see even obsolete information), so I've simply added a note to
>> the top of the page to say that the driver was removed in 2.6.35.
>
> No problem, I only saw after my patch that has also happened for the
> sk98lin(4) page.
Do you have further details for the sk98lin driver? That page then also needs
a similar note.
> My initial reflex would be that anybody interested in older stuff
> already has a habit
> with working with version control history.
As said, I prefer to hold onto the pages, at least for a while.
Cheers,
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-09-05 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 6:13 [PATCH] wavelan.4: Remove manpage for no longer available driver Elie De Brauwer
[not found] ` <1377929583-5438-1-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-04 12:38 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkj9bFt8PAp_tDCdG870XvR5CM9R=33+yV96AoWMMg3aVA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-04 19:13 ` Elie De Brauwer
[not found] ` <CAGWqfihQ6mjrygiy0Ytopx5yYfU4C7Cj6=byBH09PMXCfivAAQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-05 8:04 ` Michael Kerrisk (man-pages) [this message]
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=52283B29.4030102@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.