summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
...
* prctl.2: tfixEric Biggers2023-07-15-3/+3
| | | | | Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* man*/: Prefer off_t over off64_t for splice(2), etc.Paul Eggert2023-07-15-15/+74
| | | | | | | | | | | | | | | | | | | | | | | For the few functions that come only in 64-bit off_t flavors, document their APIs as using off_t instead of off64_t, and say also that code should #define _FILE_OFFSET_BITS 64. This documents what user code is (and should be) doing anyway, if it needs to work on traditional x86 and ARM Linux. Reported-by: Rich Felker <dalias@libc.org> Fixes: 9bebb17e5b57 ("splice.2: Use 'off64_t' instead of 'loff_t'") Fixes: 76c5631fb442 ("copy_file_range.2: Document glibc wrapper instead of kernel syscall") Fixes: 5cabfa06b407 ("man-pages 1.68") Fixes: 3ca974e3988a ("New page for sync_file_range(2), new in kernel 2.6.17.") Fixes: 9bebb17e5b57 ("sync_file_range.2: Document the architecture-specific sync_file_range2() system call") Fixes: 79bf8cdcf36a ("Document fopencookie(3), a library function that allows custom implementation of a stdio stream.") Signed-off-by: Paul Eggert <eggert@cs.ucla.edu> Reviewed-by: Sam James <sam@gentoo.org> Cc: Jonathan Wakely <jwakely@redhat.com> Cc: Szabolcs Nagy <nsz@port70.net> Cc: Jakub Wilk <jwilk@jwilk.net> Cc: A. Wilcox <AWilcox@wilcox-tech.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* dir_colors.5: Relicense pageAlejandro Colomar2023-07-15-9/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On 2023-07-08 22:14, Martin (Joey) Schulze wrote: > For the record, > > I would like to re-license dir_colors(5) under the GPLv2+ > > Please adjust the manpage source accordingly. > > .\" Copyright (c) 2001 Martin Schulze <joey@infodrom.org> > .\" > .\" This is free documentation; you can redistribute it and/or > .\" modify it under the terms of the GNU General Public License as > .\" published by the Free Software Foundation; either version 2 of > .\" the License, or (at your option) any later version. > .\" > .\" The GNU General Public License's references to "object code" > .\" and "executables" are to be interpreted as the output of any > .\" document formatting or typesetting system, including > .\" intermediate and printed output. > .\" > .\" This manual is distributed in the hope that it will be useful, > .\" but WITHOUT ANY WARRANTY; without even the implied warranty of > .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > .\" GNU General Public License for more details. > .\" > .\" You should have received a copy of the GNU General Public > .\" License along with this manual; if not, write to the Free > .\" Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, > .\" USA. > > This should help keep the manpage free and a version in Fedora. Link: <https://gitlab.com/fedora/legal/fedora-license-data/-/issues/211> Reported-by: Adam Dobes <adobes@redhat.com> Cc: Brian Inglis <Brian.Inglis@Shaw.ca> Cc: Martin (Joey) Schulze <joey@infodrom.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* statvfs.3: note f_favail = f_ffree on Linuxнаб2023-07-15-0/+8
| | | | | | | | | | | | | | | | | | | | Quoting myself from #musl: 01:59:40 hm, I think this was just invented for symmetry with bfree/bavail 02:00:46 FFS has minfree for space but nothing equivalent for inodes 02:32:31 (this is mirrored in ext4; a global grep over DragonFlyBSD and the illumos gate showed just NFSv3 forwarding from the server; OpenBSD always sets it to the same thing as f_ffree; oddly, NetBSD /does/ calculate it differently for LFS and FFS but due to queued writes or w/e not because of root reservation; and as expected a lot of "/* what to put in here? */" and "// XXX same??") Link: https://lore.kernel.org/linux-man/f54kudgblgk643u32tb6at4cd3kkzha6hslahv24szs4raroaz@ogivjbfdaqtb/t/#u Cc: Tom Schwindl <schwindl@posteo.de> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* isalpha.3: Move NOTES to CAVEATS, and clarify some Undefined BehaviorAlejandro Colomar2023-07-08-2/+4
| | | | | | Reported-by: Yedidyah Bar David <didi@redhat.com> Acked-by: Sam James <sam@gentoo.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* CONTRIBUTING, INSTALL, README, RELEASE: Reflow to 72 columnsAlejandro Colomar2023-07-08-203/+229
| | | | | | This makes it easier to quote in emails. Signed-off-by: Alejandro Colomar <alx@kernel.org>
* regex.3: ffix: "([^...])" is not an end of sentenceнаб2023-07-08-1/+1
| | | | | | | | | Caused a double space before "not". Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Tested-by: "G. Branden Robinson" <g.branden.robinson@gmail.com> Cc: Tom Schwindl <schwindl@posteo.de> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* ip.7: Document IP_LOCAL_PORT_RANGE socket optionJakub Sitnicki2023-07-08-0/+26
| | | | | | | | | | | | Linux commit 91d0b78c5177 ("inet: Add IP_LOCAL_PORT_RANGE socket option") introduced a new socket option available for AF_INET and AF_INET6 sockets. Option is available starting from Linux 6.3. Document it. Reviewed-by: Simon Horman <simon.horman@corigine.com> Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com> [alx: semantic newlines] Signed-off-by: Alejandro Colomar <alx@kernel.org>
* proc.5: Clarify that boot arguments can be embedded in imagePaul E. McKenney2023-07-08-0/+3
| | | | | | | | | | | | | | | | | With the advent of the CONFIG_BOOT_CONFIG Kconfig option, kernel boot arguments can now be embedded in the kernel image, either attached to the end of initramfs or embedded in the kernel itself. Document this possibility in the /proc/cmdline entry of proc.5. Signed-off-by: Paul E. McKenney <paulmck@kernel.org> Cc: Michael Kerrisk <mtk.manpages@gmail.com> Cc: Jonathan Corbet <corbet@lwn.net> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Nick Desaulniers <ndesaulniers@google.com> Cc: Vlastimil Babka <vbabka@suse.cz> Cc: Johannes Weiner <hannes@cmpxchg.org> Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* landlock_add_rule.2: tfixGünther Noack2023-07-08-1/+1
| | | | Signed-off-by: Alejandro Colomar <alx@kernel.org>
* fanotify_init.2: remove empty pre-header lineнаб2023-07-08-1/+1
| | | | | | | | Which yields an empty line in the formatted output. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Fixes: e9f14fa0bbc1 ("fanotify.7, fanotify_init.2: Document FAN_REPORT_DIR_FID") Signed-off-by: Alejandro Colomar <alx@kernel.org>
* inotify.7: wds are in the range [1, INT_MAX], not [0,наб2023-07-08-1/+1
| | | | | | | | | | | | | | Naturally, the first inotify_add_watch() returns 1, but also fs/notify/inotify.c:inotify_add_to_idr() allocates them with idr_alloc_cyclic(idr, i_mark, start=1, end=0, GFP_NOWAIT); (start inclusive, end exclusive). (From SYSCALL_DEFINE3(inotify_add_watch, ...), from inotify_update_watch(), from inotify_new_watch()). Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* epoll_event.3type: epoll_ctl is (2)наб2023-07-08-1/+1
| | | | | Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* prctl.2: Document PR_GET_AUXVJosh Triplett2023-07-08-0/+12
| | | | | Signed-off-by: Josh Triplett <josh@joshtriplett.org> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* poll.2: explicitly say what happens for regular files &c.наб2023-07-08-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Naively, one may consider being "ready" to mean, for example, lseek(0, 0, SEEK_END); poll({.fd = 0, .events = POLLIN}, 0); to be able to say whether new data has appeared at the end of the file. This is not the case, and poll() is only meaningful as "will a read or a write sleep": regular files and block devices are always ready to return an empty read in this case, for example, and you need to use inotify to achieve this. Under Linux this is governed by DEFAULT_POLLMASK (EPOLLIN | EPOLLOUT | EPOLLRDNORM | EPOLLWRNORM) being returned if no explicit poll operation is defined for the file. As contrast, unpollables like the above are refused by epoll_ctl(ADD). I explicitly hit the two keywords I searched for (regular, block) before just writing a test program to confirm that poll() behaved as expected and is not a good fit for my use-case. This behaviour is guaranteed by POSIX (Issue 8 Draft 3): 51381 The poll( ) and ppoll( ) functions shall support regular files, terminal and pseudo-terminal 51382 devices, FIFOs, pipes, and sockets. The behavior of poll( ) and ppoll( ) on elements of fds that refer 51383 to other types of file is unspecified. 51384 Regular files shall always poll TRUE for reading and writing. 51385 A file descriptor for a socket that is listening for connections shall indicate that it is ready for 51386 reading, once connections are available. A file descriptor for a socket that is connecting 51387 asynchronously shall indicate that it is ready for writing, once a connection has been established. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* memchr.3: rawmemchr doesn't have an n parameterнаб2023-07-08-1/+1
| | | | | | | | | | The /point/ is it's unbounded; git grep -F 'void "' | grep -F '[]' didn't return anything so I reverted it to a void*. Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz> Fixes: c64cd13e0025 ("Various pages: SYNOPSIS: Use VLA syntax in 'void *' function parameters") Signed-off-by: Alejandro Colomar <alx@kernel.org>
* boot.7: LILO is not used often anymoreAlejandro Colomar2023-07-08-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | On 6/18/23 22:05, Oskari Pirhonen wrote: > On Sat, Jun 17, 2023 at 13:11:29 +0200, Helge Kreutzmann wrote: >> Hello Alejandro, >> On Sun, Mar 12, 2023 at 12:31:37AM +0100, Alejandro Colomar wrote: >>> On 3/11/23 18:13, Helge Kreutzmann wrote: >>>> Without further ado, the following was found: >>>> >>>> Issue: This is true only on x86 and Lilo is probably not much >>>> used anymore; also systemd has its own (?) bootloader >> >> Lilo has just been removed from Debian, so to my knowledge only >> Mageia ships it. >> > > FWIW, Gentoo still has LILO in the repos. This doesn't change the > fact that it probably does not see much use anymore. Definitely not > enough to warrant being mentioned as "is often". Maybe a historical > note, if anything. Reported-by: Helge Kreutzmann <debian@helgefjell.de> Reported-by: Oskari Pirhonen <xxc3ncoredxx@gmail.com> Cc: Mario Blaettermann <mario.blaettermann@gmail.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* malloc.3: write about another possible reason for ENOMEMMasatake YAMATO2023-06-02-0/+4
| | | | | Signed-off-by: Masatake YAMATO <yamato@redhat.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
* statx.2: Fix Linux versionAlejandro Colomar2023-06-01-1/+1
| | | | | | | | | $ git describe --contains 80340fe3 v5.8-rc1~203^2~4 Fixes: 4ca216bacc7d ("statx.2: Document STAT_ATTR_MOUNT_ROOT") Reported-by: Yang Xu <xuyang2018.jy@fujitsu.com> 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>
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-01 11:14:32 +0000