Hi Rajesh,
On Thu, Dec 28, 2023 at 09:26:01PM +0530, Rajesh Pandian wrote:
> ---
Missing commit message.
> man3/dl_iterate_phdr.3 | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/man3/dl_iterate_phdr.3 b/man3/dl_iterate_phdr.3
> index 0a8beb3ae..f47fdd502 100644
> --- a/man3/dl_iterate_phdr.3
> +++ b/man3/dl_iterate_phdr.3
> @@ -129,7 +129,9 @@ The
> .I dlpi_phnum
> field indicates the size of this array.
> .P
> -These program headers are structures of the following form:
> +The ELF program header is described by the type Elf32_Phdr
> +or Elf64_Phdr depending on the architecture.
Please use semantic newlines.
$ MANWIDTH=72 man man-pages | sed -n '/Use semantic newlines/,/^$/p'
Use semantic newlines
In the source of a manual page, new sentences should be started
on new lines, long sentences should be split into lines at clause
breaks (commas, semicolons, colons, and so on), and long clauses
should be split at phrase boundaries. This convention, sometimes
known as "semantic newlines", makes it easier to see the effect
of patches, which often operate at the level of individual sen‐
tences, clauses, or phrases.
In this case, I'd break the line between 'by' and 'the', or maybe before
'depending'; whichever you prefer.
Cheers,
Alex
> +Following is an example of 32 bit architecture:
> .P
> .in +4n
> .EX
> --
> 2.39.2
>
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
Attachment:
signature.asc
Description: PGP signature
