The branch stable/12 has been updated by bapt:

URL: 
https://cgit.FreeBSD.org/src/commit/?id=ee3ebf390811f23f3215770dea037c1e2264a981

commit ee3ebf390811f23f3215770dea037c1e2264a981
Author:     Fernando ApesteguĂ­a <[email protected]>
AuthorDate: 2020-09-25 10:20:12 +0000
Commit:     Baptiste Daroussin <[email protected]>
CommitDate: 2021-09-22 10:27:46 +0000

    vi(1): Add URL to the vi/ex reference manual in the man page
    
    Reported in PR 241985
    
    The manual page references the "vi/ex reference manual" but there is no
    information about where to find that document. Add a reference to the 
manual in
    the SEE ALSO section since the Project hosts a copy of it[1].
    
    Change sent upstream[2]
    
    If D26158 gets reviewed and committed, we could close that PR.
    
    [1] https://docs.freebsd.org/44doc/usd/13.viref/paper.pdf).
    [2] https://github.com/lichray/nvi2/pull/85
    
    Submitted by:   [email protected]
    Approved by:    manpages (gbe@)
    Differential Revision:  https://reviews.freebsd.org/D26163
    
    (cherry picked from commit f1cba2b70cd1f705d7b878e7b8d9f99fe389dc7a)
---
 contrib/nvi/man/vi.1 | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/contrib/nvi/man/vi.1 b/contrib/nvi/man/vi.1
index fcbc1531d9ac..8c75e9e66a33 100644
--- a/contrib/nvi/man/vi.1
+++ b/contrib/nvi/man/vi.1
@@ -12,7 +12,7 @@
 .\" that you would have purchased it, or if any company wishes to
 .\" redistribute it, contributions to the authors would be appreciated.
 .\"
-.Dd November 2, 2013
+.Dd September 25, 2020
 .Dt VI 1
 .Os
 .Sh NAME
@@ -2743,6 +2743,10 @@ and \*(Gt0 if an error occurs.
 .Xr ctags 1 ,
 .Xr iconv 1 ,
 .Xr re_format 7
+.Rs
+.%T vi/ex reference manual
+.%U https://docs.freebsd.org/44doc/usd/13.viref/paper.pdf
+.Re
 .Sh STANDARDS
 .Nm nex Ns / Ns Nm nvi
 is close to
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/dev-commits-src-all
To unsubscribe, send any mail to "[email protected]"

Reply via email to