From: Petr Baudis <pasky-AlSwsSmVLrQ@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: "linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: man-pages-3.21 released
Date: Tue, 21 Apr 2009 11:05:29 +0200 [thread overview]
Message-ID: <20090421090528.GL21271@machine.or.cz> (raw)
In-Reply-To: <cfd18e0f0904202202l3f50bde9yd0085e0797a553e3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hullo,
On Tue, Apr 21, 2009 at 05:02:25PM +1200, Michael Kerrisk wrote:
> Gidday,
>
> The Linux man-pages maintainer proudly announces:
>
> man-pages-3.21.tar.gz - man pages for Linux
>
> This release is now available for download at:
>
> http://www.kernel.org/pub/linux/docs/man-pages
> or ftp://ftp.kernel.org/pub/linux/docs/man-pages
can you please push out your current tree?
> ==================== Changes in man-pages-3.21 ====================
>
> Released: 2009-04-15, Los Gatos
Isn't this date wrong?
> Changes to individual pages
> ---------------------------
>
> initrd.4
> Michael Kerrisk
> Various minor wording improvements
>
> initrd.4
> Frank Dana
> Add missing word in description
>
> feature_test_macros.7
> Michael Kerrisk
> Update for glibc 2.10 changes to <features.h>
> From glibc 2.10, <features.h> understands the values 200809
> for _POSIX_C_SOURCE and 700 for _XOPEN_SOURCE, and makes
> corresponding changes to defaults for other feature test macros.
So far I was guessing that man-pages are supposed only to have changes
in latest released glibc version when they aren't in flux yet. Is the
policy different? Or is it just a "common sense" policy that changes
that are obviously fixed already are included?
--
Petr "Pasky" Baudis
The average, healthy, well-adjusted adult gets up at seven-thirty
in the morning feeling just terrible. -- Jean Kerr
--
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
next prev parent reply other threads:[~2009-04-21 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 5:02 man-pages-3.21 released Michael Kerrisk
[not found] ` <cfd18e0f0904202202l3f50bde9yd0085e0797a553e3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-21 9:05 ` Petr Baudis [this message]
[not found] ` <20090421090528.GL21271-DDGJ70k9y3lX+M3pkMnKjw@public.gmane.org>
2009-04-24 16:31 ` Michael Kerrisk
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=20090421090528.GL21271@machine.or.cz \
--to=pasky-alswssmvlrq@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox