public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Michael Kerrisk <mtk-manpages@gmx.net>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: man-pages-2.59 and man-pages-2.60 are released
Date: Thu, 28 Jun 2007 19:49:42 +0600	[thread overview]
Message-ID: <4683BC76.8070805@ums.usu.ru> (raw)
In-Reply-To: <467F8FCF.4080009@gmx.net>

Michael Kerrisk wrote:

> I just released man-pages-2.59 and man-pages-2.60.
> 
> These releases are now available for download at:
> 
>     http://www.kernel.org/pub/linux/docs/manpages

There is one little problem with this: there is no stable URL for a given 
version. This hurts, e.g., automated Linux From Scratch rebuilds (the 
official script grabs the URL from the book, but it becomes invalid too soon).

Could you please, in order to avoid this, do what SAMBA team does: place 
into http://www.kernel.org/pub/linux/docs/manpages/Old not only old 
versions, but also the current version? This way, LFS will be sure that the 
2.60 version is always available as 
http://www.kernel.org/pub/linux/docs/manpages/Old/man-pages-2.60.tar.bz2 
(even if it is in fact the latest version).

Thanks in advance.

-- 
Alexander E. Patrakov

  parent reply	other threads:[~2007-06-28 13:50 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 [this message]
2007-06-28 16:17   ` Michael Kerrisk
2007-06-28 16:33     ` Alexander E. Patrakov
2007-06-28 16:54       ` Michael Kerrisk
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=4683BC76.8070805@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk-manpages@gmx.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