From owner-freebsd-current@freebsd.org  Sun Oct 29 16:17:20 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA5EFE44D05
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun, 29 Oct 2017 16:17:20 +0000 (UTC) (envelope-from ian@freebsd.org)
Received: from pmta2.delivery6.ore.mailhop.org
 (pmta2.delivery6.ore.mailhop.org [54.200.129.228])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8E380835EE
 for <freebsd-current@freebsd.org>; Sun, 29 Oct 2017 16:17:20 +0000 (UTC)
 (envelope-from ian@freebsd.org)
X-MHO-User: 7f349a84-bcc4-11e7-b50b-53dc5ecda239
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 73.78.92.27
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from ilsoft.org (unknown [73.78.92.27])
 by outbound2.ore.mailhop.org (Halon) with ESMTPSA
 id 7f349a84-bcc4-11e7-b50b-53dc5ecda239;
 Sun, 29 Oct 2017 16:16:19 +0000 (UTC)
Received: from rev (rev [172.22.42.240])
 by ilsoft.org (8.15.2/8.15.2) with ESMTP id v9TGHCka001400;
 Sun, 29 Oct 2017 10:17:12 -0600 (MDT) (envelope-from ian@freebsd.org)
Message-ID: <1509293832.21609.7.camel@freebsd.org>
Subject: Re: FreeBSD Documentation
From: Ian Lepore <ian@freebsd.org>
To: Allan Jude <allanjude@freebsd.org>, freebsd-current@freebsd.org
Date: Sun, 29 Oct 2017 10:17:12 -0600
In-Reply-To: <f5415cb5-939c-70d2-907e-37293f93bdd5@freebsd.org>
References: <CALM2mEmS4hX+crw0MOkvPegcJ5_pqth6MduL8Q0O=SiN6ZkU5Q@mail.gmail.com>
 <20171029150039.GL34891@home.opsec.eu>
 <f5415cb5-939c-70d2-907e-37293f93bdd5@freebsd.org>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Oct 2017 16:17:20 -0000

On Sun, 2017-10-29 at 11:37 -0400, Allan Jude wrote:
> On 2017-10-29 11:00, Kurt Jaeger wrote:
> > 
> > Hi!
> > 
> > > 
> > > How can we suggest edits for the docs?
> > Checkout the docs repo:
> > 
> >   svn checkout https://svnweb.freebsd.org/doc/head/ .
> > 
> > Change the relevant files, create a new problem report on
> > 
> >   https://bugs.freebsd.org/
> > 
> > and attach the svn diff to that problem report.
> > 
> Since the document in question is a man page, it actually lives in
> the
> src tree.
> 
> svn checkout https://svn.freebsd.org/base/head/ .
> 
> cd usr.sbin/jail
> 
> vi jail.8
> 
> svn diff > jail_manpage.patch
> 
> And then attach that patch to a bugzilla, or upload it to
> reviews.freebsd.org
> 
> 

I hope I'm right in thinking that just submitting the proposed changes
as plain text would also be an option?  I suspect there are more people
with good ideas on improving manpages than there are people who've
decided they really want to learn the arcane skill of manpage markup
language.

-- Ian