From 38f293795cde2a7e32524b08c591ba612853137f Mon Sep 17 00:00:00 2001
From: Michael Kerrisk
diff --git a/licenses.html b/licenses.html
index 5973b6c..c88b5d3 100644
--- a/licenses.html
+++ b/licenses.html
@@ -139,7 +139,7 @@ Subject: Re: [RFC v4] system_data_types.7: Document sigval, ssize_t, suseconds_t
by including the following text at the top
of the page source, and substituting the appropriate pieces.
Licensing under GPLv2 is preferred, because so far only v2 of
- the GPL is used in any man pages, and I'd prefer to avoid
+ the GPL is used in any man pages, and we'd prefer to avoid
further license proliferation.
Following a session (Who own's the interface) - that I led at the 2008 Linux Plumbers Conference, + that led by Michael Kerrisk at the 2008 Linux Plumbers Conference, the linux-api mailing list (linux-api@vger.kernel.org) - was - created at my request - as a forum to discuss + was created as a forum to discuss changes that affect the Linux programming interface (API or ABI).
diff --git a/maintaining.html b/maintaining.html index 6bd9880..25cb8cd 100644 --- a/maintaining.html +++ b/maintaining.html @@ -46,11 +46,13 @@ Maintaining Linux man-pages The current man-pages maintainer is (since 2004) Michael Kerrisk (mtk.manpages@gmail.com; - blog). + blog); + starting in 2020, Alejandro Colomar + (alx.manpages@gmail.com) + has joined as comaintainer.- One day, someone else will be the maintainer. - So, to make life easier for the next person: + This page provides some tips on how to maintain the Linux man-pages project (also useful for anyone who wants to help with work on man-pages). @@ -185,7 +187,7 @@ Maintaining Linux man-pages One of the biggest challenges is keeping up to date with changes in the kernel and glibc. There are a few ways to do this. - This section lists the things I find most useful. + This section lists some of the most useful ways.
@@ -246,8 +248,8 @@ Maintaining Linux man-pages Below are some other ways of trying to discover changes in the kernel and glibc. There's way too much information here to track (in particular, it's pretty much impossible to track all of - of the mailing lists), but I keep this list as a way - of reminding myself of where useful pieces of info could be found. + of the mailing lists), but the list below serves as a reminder of + some places where useful information could be found.- Perhaps some other distributions have similar facilities, - but these are the - only ones I know about so far. -
- -- Below is a list of pages that I would like - to see in the man-pages set. + Below is a list of pages that probably should be added + to the man-pages set. If you are thinking of writing one or more of these pages, then:
- mtk.manpages@gmail.com - (Please do not CC my - @man7.org email address.) -- CC -
- linux-man@vger.kernel.org - (no HTML mail please) -- and CC any other interested parties, + Submit the page following the project guidelines for + submitting patches. + Be sure to CC any other interested parties, including any people that you know of who might be suitable reviewers for the page.
- The above is the minimum needed to ensure that - there's some chance I'll see the patch. - (If you did that, and I do not respond, then ping the mail thread, - "replying to all". - Unfortunately, I get more mail than I can sometimes deal with, - and things do get lost.) + The above is the minimum needed so that someone + might respond to your patch. + (If you did that, and someone does not respond within a few days, + then ping the mail thread, "replying to all".)
To make your patch even more useful, @@ -167,7 +170,7 @@ patches |
- mtk.manpages@gmail.com - (Please do not CC my - @man7.org email address.) - and CC - linux-man@vger.kernel.org - (no HTML mail please), -+ can be reported by sending an email message to the + maintainers + and CCing + linux-man@vger.kernel.org + (no HTML mail please), Please do not report such bugs via the bugzilla. @@ -182,8 +178,8 @@ bugs |
- Note: I am doubtful that the problem noted in + Note: I (mtk) am doubtful that the problem noted in the above point could be resolved via some "include" mechanism that includes relevant pieces from the Section 2 page into the Section 3 page. -- cgit v1.2.3