diff options
author | Michael Kerrisk <mtk.manpages@gmail.com> | 2020-11-09 12:06:50 +0100 |
---|---|---|
committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2020-11-09 12:06:50 +0100 |
commit | 1b21aed4a33ad03e256b425e363c98e163f6cde7 (patch) | |
tree | 6ebea11f72af8f10c8b6faa081b35dc3d10a6070 | |
parent | 25a49914e605be79f3a10788418d6465a10caebf (diff) | |
download | website-1b21aed4a33ad03e256b425e363c98e163f6cde7.tar.gz |
maintaining.html: Remove crufty comment that long ago ceased to be relevant
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r-- | maintaining.html | 18 |
1 files changed, 0 insertions, 18 deletions
diff --git a/maintaining.html b/maintaining.html index 00308f3..640c372 100644 --- a/maintaining.html +++ b/maintaining.html @@ -843,24 +843,6 @@ subscribe linux-net in the message body to majordomo@vger.kernel.org </ul> -<!-- -<h3>Release philosophy</h3> - - <p> - If you make sweeping <em>formatting</em> - changes to a large number of pages, - separate them out into their own release that contains - minimal <em>content</em> changes. - This makes it easier for the people - that want to verify content changes independently of the change log. - Yes, some people actually - <span class="cmd">diff</span> - each release to see what changed; - for example, some downstream maintainers and translators of - the man pages sometimes like to do this. - </p> ---> - <h2>Being a good free software citizen</h2> |