From bbc5c8ee329ce4167c37a7924439806952fbc12b Mon Sep 17 00:00:00 2001
From: Conrad Meyer <cem@FreeBSD.org>
Date: Sat, 28 Jul 2018 19:08:00 +0000
Subject: [PATCH] Clean up execl*(3) manual page prototype formatting

Rendering of execle was missing a comma between the NULL argument and envp.

For unclear reasons, POSIX' definition of these routines comments out the
mandatory trailing NULL argument.  That seems unnecessary and probably
(reasonably) confuses mdoc.

For unclear reasons, POSIX' definition of these routines spells NULL as
"(char *)0."  This is needlessly unclear.  One guess might be that POSIX
targets more exotic computer architectures than FreeBSD does.  Fortunately,
there is no such problem on any reasonable platform for FreeBSD to support.
Spell NULL as NULL.

The comma was probably removed in r117204 while the comment and creative
spelling of NULL were added in r116537 (both 15 years ago).
---
 lib/libc/gen/exec.3 | 13 ++++---------
 1 file changed, 4 insertions(+), 9 deletions(-)

diff --git a/lib/libc/gen/exec.3 b/lib/libc/gen/exec.3
index a0ff4149a46..2fbdaa7f609 100644
--- a/lib/libc/gen/exec.3
+++ b/lib/libc/gen/exec.3
@@ -28,7 +28,7 @@
 .\"     @(#)exec.3	8.3 (Berkeley) 1/24/94
 .\" $FreeBSD$
 .\"
-.Dd January 5, 2016
+.Dd July 28, 2018
 .Dt EXEC 3
 .Os
 .Sh NAME
@@ -46,16 +46,11 @@
 .In unistd.h
 .Vt extern char **environ ;
 .Ft int
-.Fn execl "const char *path" "const char *arg" ... /* "(char *)0" */
+.Fn execl "const char *path" "const char *arg" ... NULL
 .Ft int
-.Fn execlp "const char *file" "const char *arg" ... /* "(char *)0" */
+.Fn execlp "const char *file" "const char *arg" ... NULL
 .Ft int
-.Fo execle
-.Fa "const char *path" "const char *arg" ...
-.Fa /*
-.Bk -words
-.Fa "(char *)0" "char *const envp[]" */
-.Ek
+.Fn execle "const char *path" "const char *arg" ... NULL "char *const envp[]"
 .Fc
 .Ft int
 .Fn exect "const char *path" "char *const argv[]" "char *const envp[]"