Hi Petr, 2009/4/21 Petr Baudis <pasky@xxxxxxx>: > 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? Done. Sorry -- I was on the move quite a bit, and then stuck behind a rather restrictive firewall. >> ==================== Changes in man-pages-3.21 ==================== >> >> Released: 2009-04-15, Los Gatos > > Isn't this date wrong? I don't think so. Why do you? (But, it's true that my announcement went out a few days after I posted the tarball.) >> 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? It's "common sense" -- if I see something that is clearly destined for a release soon, and I can easily document it, I will. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
