All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: Michael Kerrisk <mtk-manpages@gmx.net>
Cc: Bill Davidsen <davidsen@tmr.com>,
	rob@landley.net, linux-kernel@vger.kernel.org
Subject: Re: man-pages-2.59 and man-pages-2.60 are released
Date: Fri, 29 Jun 2007 14:55:55 +0600	[thread overview]
Message-ID: <4684C91B.5060203@ums.usu.ru> (raw)
In-Reply-To: <20070629083021.58530@gmx.net>

Michael Kerrisk wrote:

> Well, I think all that LFS seems to want is links that are
> stable "for a while" (since I don't suppose that they want
> to use really old tarballs in any case). So, for 
> the benefit of LFS, I'll just be less aggressive about
> moving tarballs into "Old" (I'll leave them sitting in http://www.kernel.org/pub/linux/docs/manpages/
> for a few months at least.)

If this helps, here is the version information.

Stable LFS (version 6.2, released on August 3, 2006) tells users to download 
man-pages 2.34 (two releases old at that time). LFS-6.3 is expected to be 
released in two months or so, thus a one-year period before moving tarballs 
to "Old" should be enough even for stable LFS books (and if we agree on 
that, I'll close http://wiki.linuxfromscratch.org/lfs/ticket/2037 as invalid).

Thanks for cooperation.

-- 
Alexander E. Patrakov

  reply	other threads:[~2007-06-29  8:55 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
2007-06-28 22:52     ` Bill Davidsen
2007-06-29  8:30       ` Michael Kerrisk
2007-06-29  8:55         ` Alexander E. Patrakov [this message]
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=4684C91B.5060203@ums.usu.ru \
    --to=patrakov@ums.usu.ru \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk-manpages@gmx.net \
    --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 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.