In message <[email protected]>, Allan Jude 
write
s:
> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> --aGGixulc9uAFLFA2k9VWxk7NcN6fQBdFP
> Content-Type: multipart/mixed; boundary="T6pjExsFmnQlcvXFRkfkRKJem0LXImVKi";
>  protected-headers="v1"
> From: Allan Jude <[email protected]>
> To: [email protected]
> Message-ID: <[email protected]>
> Subject: Re: FreeBSD Documentation
> References: <[email protected]
> om>
>  <[email protected]>
> In-Reply-To: <[email protected]>
> 
> --T6pjExsFmnQlcvXFRkfkRKJem0LXImVKi
> Content-Type: text/plain; charset=utf-8
> Content-Language: en-US
> Content-Transfer-Encoding: quoted-printable
> 
> On 2017-10-29 11:00, Kurt Jaeger wrote:
> > Hi!
> >=20
> >> How can we suggest edits for the docs?
> >=20
> > Checkout the docs repo:
> >=20
> >   svn checkout https://svnweb.freebsd.org/doc/head/ .
> >=20
> > Change the relevant files, create a new problem report on
> >=20
> >   https://bugs.freebsd.org/
> >=20
> > and attach the svn diff to that problem report.
> >=20
> 
> 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

Yes, and that's the first step to becoming a committer. I recall sending 
multiple patches because I didn't want to patch brand new FreeBSD systems 
after installing the ISO (they were plastic discs then). (We used FreeBSD 
for infrastructure servers at $JOB at the time.) Then one day there was an 
email from nectar@ in my inbox offering the keys to the farm.


-- 
Cheers,
Cy Schubert <[email protected]>
FreeBSD UNIX:  <[email protected]>   Web:  http://www.FreeBSD.org

        The need of the many outweighs the greed of the few.


_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[email protected]"

Reply via email to