All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
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: Tue, 26 Jun 2007 09:34:10 -0400	[thread overview]
Message-ID: <200706260934.10620.rob@landley.net> (raw)
In-Reply-To: <467F8FCF.4080009@gmx.net>

On Monday 25 June 2007 05:50:07 Michael Kerrisk wrote:
> Gidday,
>
> I just released man-pages-2.59 and man-pages-2.60.

Could you make a man-pages-latest symlink in the download directory?

I'm trying to keep an HTML copy of this (converted with doclifter) up to date 
(It'll be on http://kernel.org/doc after OLS but right now it's just at 
http://landley.net/kdocs/xmlman and yes I know the symlinks are screwed up, 
and there are inappropriate UTF-8 squigglies without the accompanying code 
page declaration.  Doclifter bugs, I'm working on it...)

Anyway, I only intermittently spot these notices going by on the list.  
Something I could check from a cron job would be nicer...

Thanks,

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

  reply	other threads:[~2007-06-26 13:34 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 [this message]
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
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=200706260934.10620.rob@landley.net \
    --to=rob@landley.net \
    --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 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.