diff options
| author | Alejandro Colomar <alx@kernel.org> | 2022-10-20 18:27:43 +0200 |
|---|---|---|
| committer | Alejandro Colomar <alx@kernel.org> | 2022-10-20 18:27:56 +0200 |
| commit | a15e8c33927f8360e67e621a0b48f04a2d76f7f5 (patch) | |
| tree | 42466e604b358f9eb3a9892d02a86d46f8c800e8 | |
| parent | 146f6325d9800dcc2250e9bb126aff6543b9c277 (diff) | |
| download | man-pages-a15e8c33927f8360e67e621a0b48f04a2d76f7f5.tar.gz | |
RELEASE, man-pages-6.01.Announce: Remove .Announce file
Signed-off-by: Alejandro Colomar <alx@kernel.org>
| -rw-r--r-- | RELEASE | 31 | ||||
| -rw-r--r-- | man-pages-6.01.Announce | 61 |
2 files changed, 6 insertions, 86 deletions
@@ -39,26 +39,7 @@ but in that commit log you can check a few commands that will help. $ git commit -sm "Changes: Ready for ${new}" -3) Announce ------------ - -Rename the file with the version that will be released, and update the -contents. Check old commits, like c11cb1ca844d "Ready for 6.01". - -- Update the version number in the tarball name. - -- Rename the file: - - $ mv man-pages-${old}.Announce man-pages-${new}.Announce - -- Commit: - - $ git add man-pages-${old}.Announce - $ git add man-pages-${new}.Announce - $ git commit -sm "Announce: Ready for ${new}" - - -4) Tag +3) Tag ------ Create a signed tag. The tag message should note the most important @@ -72,7 +53,7 @@ relevant for them. Check old tags such as 'man-pages-6.00' or $ git tag -s man-pages-${new} -5) Tarball +4) Tarball ---------- Creating the tarball will embed in the manual pages both the version @@ -102,7 +83,7 @@ available at <lib/dist.mk>, and any makefiles included by that one. $ cd .. -6) lsm +5) lsm ------ Rename the file with the version that has been released, and update the @@ -127,7 +108,7 @@ contents. Check old commits, like c11cb1ca844d "Ready for 6.01". - Send (email) the .lsm file to <lsm@qqx.org> with the subject "add". -7) Email +6) Email -------- Send an announce email to linux-man, LKML, libc-alpha, and possibly @@ -142,7 +123,7 @@ such as The subject of the email should be "man-pages-${new} released". -8) Changes.old +7) Changes.old -------------- Move the contents of Changes to Changes.old, and prepare for the next @@ -163,7 +144,7 @@ release. $ git commit -sm "Start of man-pages-NEXT: Move Changes to Changes.old" -9) Push +8) Push ------- You've finished. When you confirm it's good, push to the git repository. diff --git a/man-pages-6.01.Announce b/man-pages-6.01.Announce deleted file mode 100644 index 1411b05ae3..0000000000 --- a/man-pages-6.01.Announce +++ /dev/null @@ -1,61 +0,0 @@ -RELEASE -The Linux man page maintainer proudly announces. . . - - man-pages-6.01.tar.gz - man pages for Linux - -Differences from the previous manual pages release are listed in -the file "Changes". - -For further information, visit http://www.kernel.org/doc/man-pages/ - -THE PAGES -These pages are most of the section 2, 3, 4, 5, 7 man pages -for Linux. A few pages are provided in sections 1 and 8 for commands -that are not documented in other packages, and there are a few pages -in sections 5 and 8 for the timezone utilities. - -[The timezone pages were taken from -ftp://elsie.nci.nih.gov/pub/tzcode2001a.tar.gz.] -[The section 3 man pages for the db routines have been taken from -ftp://ftp.terra.net/pub/sleepycat/db.1.86.tar.gz.] -[The rpc man pages were taken from the 4.4BSD-Lite CDROM.] - -Here is a breakdown of what this distribution contains: - - Section 1 = user commands (intro, plus a few other pages) - Section 2 = system calls - Subsection 2type = types provided by the kernel - Section 3 = library calls - Subsection 3const = library constants - Subsection 3head = library header files - Subsection 3type = library types - Section 4 = devices (e.g., hd, sd) - Section 5 = file formats and configuration files (e.g., wtmp, /etc/passwd) - Section 6 = games (intro only) - Section 7 = overviews, conventions, macro packages, etc. - Section 8 = system administration (intro, plus a few other pages) - - This package contains no, or very few, section 1, 6, and 8 man pages - because these should be distributed with the binaries they are written - for. Sometimes Section 9 is used for man pages describing parts of - the kernel. - - Note that only Section 2 is rather complete, but Section 3 contains - several hundred man pages. If you want to write some man pages, - or suggest improvements to existing pages, please visit - http://www.kernel.org/doc/man-pages/ . - - -Copyright information: - - These man pages are distributed under a variety of copyright licenses. - Although these licenses permit free distribution of the nroff sources - contained in this package, commercial distribution may impose other - requirements (e.g., acknowledgement of copyright or inclusion of the - raw nroff sources with the commercial distribution). - If you distribute these man pages commercially, it is your - responsibility to figure out your obligations. (For many man pages, - these obligations require you to distribute nroff sources with any - pre-formatted man pages that you provide.) Each file that contains - nroff source for a man page also contains the author(s) name, email - address, and copyright notice. |