summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* zlibVersion.3: Add pagezlibAlejandro Colomar2023-05-31-0/+66
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: Remove all pagesAlejandro Colomar2023-05-30-288732/+0
| | | | | | | | | | | | This commit will start a new branch with no pages at all. It's intended to be useful for other projects that want to test their pages, so that they just need to check out this branch and copy the files into man*/. Then, all the existing targets in the Makefile would be available to be run on those pages. Since we support mdoc(7), and even pages with ':' in their file names since recently, I expect this to be universally usable. Signed-off-by: Alejandro Colomar <alx@kernel.org>
* unshare.2: ffix: indentation inconsistenciesGünther Noack2023-05-26-2/+2
| | | | | Signed-off-by: Günther Noack <gnoack@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* malloc.3: srcfixJakub Wilk2023-05-26-1/+1
| | | | | Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* ddp.7: Relicense to Linux-man-pages-copyleftAlejandro Colomar2023-05-26-6/+1
| | | | | | | | Alan Cox gave me explicit permission to relicense it for consistency with the rest of the project. Cc: Alan Cox <alan@llwyncelyn.cymru> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* proc.5: Clarify the format of /proc/$PID/cmdlineGünther Noack2023-05-25-2/+13
| | | | | | | | | | It is possible to produce /proc/$PID/cmdline files which do not follow the NUL-seperated format, by using the tricks described in the paragraph below. Signed-off-by: Günther Noack <gnoack@google.com> [ fix semantic newlines ] Signed-off-by: Alejandro Colomar <alx@kernel.org>
* List a fifth condition when iconv(3) may stop.Bruno Haible2023-05-25-1/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The wording regarding transliteration is vague, because this man page is not the right place for going into the details of the transliteration. Here are the details: GNU libc and GNU libiconv support transliteration, for example, of "½" to "1/2", or of "å" to "aa" in a Danish locale. The transliteration maps a multibyte character of the input encoding to zero or more characters in the output. There are two kinds of transliteration rules: - Those that are valid regardless of locale. Typically this means that the original and the transliterated character have similar glyphs, such as in the case "½" to "1/2". In GNU libc, these are collected in the files glibc/localedata/locales/translit_*. - Those that are valid in a single locale only. Often such a rule reflects similar pronounciation of the original and the transliterated characters. Some locales have script-based transliteration, for example from the Cyrillic script to the Latin script. In GNU libc, these are collected in the file glibc/localedata/locales/<locale>. In GNU libiconv, transliterations of this kind are not supported. Link: https://sourceware.org/bugzilla/show_bug.cgi?id=29913#c4 Link: https://bugzilla.kernel.org/show_bug.cgi?id=217059 Reported-by: Steffen Nurpmeso <steffen@sdaoden.eu> Reported-by: Reuben Thomas <rrt@sc3d.org> Signed-off-by: Bruno Haible <bruno@clisp.org> [ fix semantic newlines ] Signed-off-by: Alejandro Colomar <alx@kernel.org>
* statx.2: Document STAT_ATTR_MOUNT_ROOTYang Xu2023-05-24-0/+4
| | | | | | | | | | | Linux 5.10 adds STATX_ATTR_MOUNT_ROOT support. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80340fe3605c Add the text to the statx man page. Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com> [ alx: ffix ] Signed-off-by: Alejandro Colomar <alx@kernel.org>
* putenv.3: tfixнаб2023-05-24-1/+1
| | | | | | Fixes: commit b324e17d3208c940622ab192609b836928d5aa8d ("Many pages: wfix") Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* putenv.3: Originated in SysVr2; in 4.3BSD-Reno; fixed on modern systemsнаб2023-05-24-2/+3
| | | | | | | | | | | | | | | Fixed in: NetBSD 6 src lib/libc/stdlib/putenv.c 1.13 FreeBSD 7 putenv(3) says so OpenBSD 4.6 src lib/libc/stdlib/setenv.c 1.10 and is correct under current(?) MacOS as well The current wording implies that all of 4.4BSD's descenants also carry this bug (at least it did to me): they did until like 2009 but they're fine now Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* bash_aliases: Increase robustness of sed_rm_ccomments()Alejandro Colomar2023-05-24-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Thanks to perl(1), we can use a non-greedy match to remove several C89-style comments in the same line. And by splitting (and slightly modifying) the other sed(1) call, we can handle multi-line comments that start in the same line that the previous one ends. Now the only remaining issue is nested comments, but that's rare, so let's ignore it for now. $ cat com.c /* let's see */ int foo/*how about here?*/; // meh int bar; /* Let's see how this behaves */ int baz; /* like this? like that! */ int qwe; // asdasd $ sed_rm_ccomments <com.c int foo; int bar; int baz; int qwe; Here's what can and will be problematic: // /* int foo; /* */ Signed-off-by: Alejandro Colomar <alx@kernel.org>
* .mailmap: Add Serge HallynAlejandro Colomar2023-05-21-0/+3
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* .mailmap: Add Andrew ClaytonAlejandro Colomar2023-05-21-0/+2
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* .mailmap: Add Ingo SchwarzeAlejandro Colomar2023-05-21-0/+2
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* open.2, prctl.2: SYNOPSIS: Document these as variadic functionsAlejandro Colomar2023-05-20-8/+8
| | | | | | | | | | | | | I remember I discussed this with Michael Kerrisk a long ago and we agreed to apply this fix, as I felt that using overload syntax was confusing (especially since C doesn't allow overloads), but then I didn't feel urged to write a patch. Florian confirmed recently that this is confusing to more programmers, so let's do it. Link: <https://bugzilla.kernel.org/show_bug.cgi?id=216876#c1> Reported-by: Florian Weimer <fweimer@redhat.com> Cc: Michael Kerrisk <mtk.manpages@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* posix_memalign.3: Update aligned_alloc(3) to match C17DJ Delorie2023-05-20-3/+2
| | | | | | | | | | Link: <https://sourceware.org/pipermail/libc-alpha/2023-May/147810.html> Link: <https://patchwork.sourceware.org/project/glibc/patch/33ec9e0c1e587813b90e8aa771c2c8e6e379dd48.camel@posteo.net/> Link: <https://lore.kernel.org/linux-man/d79b505c-5b19-331c-5b25-d40adc9cc843@wanadoo.fr/> Cc: John Scott <jscott@posteo.net> Cc: Paul Floyd <pjfloyd@wanadoo.fr> Signed-off-by: DJ Delorie <dj@redhat.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* system_data_types.7: tfixEric Wong2023-05-20-2/+2
| | | | | | | The actual field names omit the 'g', matching sigevent.7. Signed-off-by: Eric Wong <e@80x24.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* .mailmap: Add Bruno HaibleAlejandro Colomar2023-05-19-0/+1
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* README: tfixAlejandro Colomar2023-05-19-1/+1
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* fflush.3, unlocked_stdio.3: SYNOPSIS: The streams can be nullAlejandro Colomar2023-05-18-2/+2
| | | | | Cc: Xi Ruoyao <xry111@xry111.site> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: Use -wbreak in TROFFFLAGS, and -ww in NROFFFLAGSAlejandro Colomar2023-05-09-1/+2
| | | | | | | | | | | | | | | | We don't need to see all warnings everywhere we call troff(1). Instead, put all warnings in nroff mode, which we only run for the warnings, and then only ask for warnings that depend on the output in other invocations of troff(1). -wbreak happens to enable only and all so-called "output warnings". It is an implementation detail of groff(1), but that's the best we can do now. If groff(1) changes their warnings organization, we'll need to adapt to it. Link: <https://lists.gnu.org/archive/html/groff/2023-05/msg00046.html> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* mbind.2: Clarify MPOL_MF_MOVE with MPOL_INTERLEAVE policyMike Kravetz2023-05-05-0/+10
| | | | | | | | | | There was user confusion about specifying MPOL_MF_MOVE* with MPOL_INTERLEAVE policy [1]. Add clarification. [1] https://lore.kernel.org/linux-mm/20230501185836.GA85110@monkey/ Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* resolv.conf.5: tfixJakub Wilk2023-05-05-1/+1
| | | | | Signed-off-by: Jakub Wilk <jwilk@jwilk.net> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* sched_yield.2: Rename NOTES to CAVEATS, and reorder contentsAlejandro Colomar2023-05-03-12/+12
| | | | | | | | | | Put the last paragraph at the top of the CAVEATS section, since it's probably the most important for readers. This system call is likely not the right one for most programs; let's discourage its use. Link: <https://www.realworldtech.com/forum/?threadid=189711&curpostid=189752> Cc: Andrew Clayton <a.clayton@nginx.com> Signed-off-by: Alejandro Colomar <alx@nginx.com>
* sched_yield.2: NOTES: Remove misleading sentenceAlejandro Colomar2023-05-03-5/+0
| | | | | | | | | sched_yield(2) is not the right thing for heavily contended resources. The right thing to do is to call functions that wake the waiting threads. Link: <https://www.realworldtech.com/forum/?threadid=189711&curpostid=189752> Cc: Andrew Clayton <a.clayton@nginx.com> Signed-off-by: Alejandro Colomar <alx@nginx.com>
* sched_yield.2: HISTORY: POSIX.1-2008 makes this non-optionalAlejandro Colomar2023-05-03-8/+10
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* malloc.3: SYNOPSIS: Add the _Nullable qualifierAlejandro Colomar2023-05-03-3/+3
| | | | | | These functions accept NULL. Signed-off-by: Alejandro Colomar <alx@kernel.org>
* malloc.3: ffixAlejandro Colomar2023-05-03-5/+5
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/, man.ignore.grep: srcfix; warn about blank linesAlejandro Colomar2023-05-03-2783/+2779
| | | | | | | | - Use the dummy character to avoid warnings in examples. - Re-enable the warning. Suggested-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk, *.grep: Move grep patterns to .grep filesAlejandro Colomar2023-05-02-18/+27
| | | | | | | | This simplifies the makefiles, and has the benefit that we can edit them without editing the makefile (thus without causing unnecessary rebuilds). Suggested-by: Bjarni Ingi Gislason <bjarniig@simnet.is> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* ascii.7: ffixAlejandro Colomar2023-05-02-17/+5
| | | | | | Simplify formatting of ASCII tables. Signed-off-by: Alejandro Colomar <alx@kernel.org>
* uri.7: ffixAlejandro Colomar2023-04-30-20/+79
| | | | | | Reported-by: groff(1) (`make build-catman-troff`) Cowritten-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: srcfixAlejandro Colomar2023-04-29-7/+5
| | | | | Reported-by: groff(1) (`make build-catman-troff`) Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: ffixAlejandro Colomar2023-04-29-10/+10
| | | | | Reported-by: groff(1) (`make built-catman-troff`) Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: build-catman-troff: Silence warnings about using UCAlejandro Colomar2023-04-29-0/+1
| | | | | | | | We have some pages that come from UCB, and therefore need that macro. It's not like we're going to accidentally use that macro, so let's ignore the warning. Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: build-catman-troff: Silence warnings about using PDAlejandro Colomar2023-04-29-0/+1
| | | | | | It's the best tool for certain purposes (at least, so far). Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: build-catman-troff: Silence warnings about blank lines in inputAlejandro Colomar2023-04-29-0/+1
| | | | | | | | Ideally, we want this warning, but it has false positives in the example programs, so let's disable it for now. Hopefully, groff will split those two, and then we'll be able to re-enable the one we want. Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: install-man: Ignore pages in non-standard source MANDIRSAlejandro Colomar2023-04-29-12/+12
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: build-catman-troff: Silence warnings about missing fifth argumentAlejandro Colomar2023-04-29-1/+4
| | | | | | | | This happens when the second argument is a subsection, and the warning is right because the page ends up with no section title, but let's forget about it for now. Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: Allow non-standard source MANDIRSAlejandro Colomar2023-04-29-4/+4
| | | | | | | | | | Some projects don't store their source manual pages in a directory structure resembling $MANPATH. Allow such a directory structure so that we can for example lint groff's source manual pages: $ make check lint MANDIR=~/src/gnu/groff; Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: Don't rmdirAlejandro Colomar2023-04-29-45/+3
| | | | | | | | | | There's no need; we can leave empty dirs on 'make uninstall', and it allows some simplifications. We don't need the FORCE target anymore, and don't need some directory variables either. While at it, I found some unused variable that should have been removed a long time ago: $installdirs_manX Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: MANEXT: Support man pages with .man and/or .in suffixesAlejandro Colomar2023-04-29-1/+1
| | | | | | | | | | | Those are common in some projects in their source pages; especially '.in' when it's a template that will be completed by the build system. This allows linting other projects' pages by running a command like: $ make lint MANDIR=/home/alx/src/nginx/unit/master/docs/man Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: lint-mdoc-mandoc: Silence warning about referenced manuals not foundAlejandro Colomar2023-04-28-0/+1
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: lint-mdoc-mandoc: Silence warnings about ISO 8601 format in the dateAlejandro Colomar2023-04-28-0/+1
| | | | | | ISO 8601 is the standard way to express a date. Don't warn about it. Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: lint-mdoc-mandoc: Silence warnings about lowercase in DtAlejandro Colomar2023-04-28-0/+1
| | | | | | | | | See commit 4896a4f8c4b8 ("lint-man.mk: lint-man-mandoc: Silence warnings about lowercase in TH") Cc: Ingo Schwarze <schwarze@openbsd.org> Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: Fix error detectionAlejandro Colomar2023-04-28-2/+2
| | | | | | | | See also this commit: 0440d04f8317 ("lint-man.mk: lint-man-groff-eqn: Fix error detection") Reported-by: Ralph Corderoy <ralph@inputplus.co.uk> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: Rewrite pipelines to make it easier to ignore some warningsAlejandro Colomar2023-04-28-18/+18
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: Move -T$NROFF_OUT_DEVICE into NROFFFLAGSAlejandro Colomar2023-04-28-5/+4
| | | | | | This avoids breaking some long lines. Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: Move -rCHECKSTYLE to NROFFFLAGSAlejandro Colomar2023-04-28-8/+8
| | | | | | | Having that in TROFFFLAGS caused repeated warnings for every different format we produce. Let's have these warnings only in nroff mode. Signed-off-by: Alejandro Colomar <alx@kernel.org>
* *.mk: Keep error messages in stderrAlejandro Colomar2023-04-28-9/+9
| | | | | | | We redirected them to stdout for some filtering, but forgot to put it back where it belongs. Signed-off-by: Alejandro Colomar <alx@kernel.org>
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-17 08:21:37 +0000