From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
Cc: rob@landley.net, linux-kernel@vger.kernel.org
Subject: Re: man-pages-2.59 and man-pages-2.60 are released
Date: Thu, 28 Jun 2007 18:54:05 +0200 [thread overview]
Message-ID: <20070628165405.32040@gmx.net> (raw)
In-Reply-To: <4683E2CB.8090100@ums.usu.ru>
> Michael Kerrisk wrote:
> > How about a link in /pub/linux/docs/manpages/ of the form
> > "LATEST-IS-m.xy"? Rob Landley was wanting something like this,
> > and I guess it would be easy for LFS to build a simple
> > script that looks for that link and deduces "man-pages-m.xy"
> > from it. (I've just now created such a link in the directory,
> > as an example.)
>
> We don't care about the latest version, so the link neither helps nor
> hurts us. What's needed is that the URL and the MD5 sum for a
> version in the book
> don't change, and that LFS developers have a reasonable time (say, two
> weeks) to react to version updates.
Don't change for how long? As I said, old versions never were
available "forever" on kernel.org -- usually they only stayed a
few months, though lately the lifetime stretched out a little.
I don't really want to, for example, copy the tarball to
two places each time. That takes me extra time, and is prone
to errors (e.g., I might forget).
Cheers,
Michael
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance?
Grab the latest tarball at
http://www.kernel.org/pub/linux/docs/manpages ,
read the HOWTOHELP file and grep the source
files for 'FIXME'.
next prev parent reply other threads:[~2007-06-28 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 9:50 man-pages-2.59 and man-pages-2.60 are released Michael Kerrisk
2007-06-26 13:34 ` Rob Landley
2007-06-28 13:49 ` Alexander E. Patrakov
2007-06-28 16:17 ` Michael Kerrisk
2007-06-28 16:33 ` Alexander E. Patrakov
2007-06-28 16:54 ` Michael Kerrisk [this message]
2007-06-28 22:52 ` Bill Davidsen
2007-06-29 8:30 ` Michael Kerrisk
2007-06-29 8:55 ` Alexander E. Patrakov
2007-06-29 9:36 ` Michael Kerrisk
2007-06-29 9:56 ` Alexander E. Patrakov
2007-06-29 14:33 ` Rob Landley
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=20070628165405.32040@gmx.net \
--to=mtk-manpages@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@ums.usu.ru \
--cc=rob@landley.net \
/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