Date: Fri, 5 Sep 2003 15:28:47 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: "Daniel C. Sobral" <dcs@tcoip.com.br> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/net if_ethersubr.c Message-ID: <20030905152847.2571f544.Alexander@Leidinger.net> In-Reply-To: <3F588AC4.5080001@tcoip.com.br> References: <20030830023923.Q811@odysseus.silby.com> <Pine.NEB.3.96L.1030830102835.47993J-100000@fledge.watson.org> <20030831144531.17d722da.Alexander@Leidinger.net> <3F588AC4.5080001@tcoip.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 05 Sep 2003 10:08:20 -0300
"Daniel C. Sobral" <dcs@tcoip.com.br> wrote:
> Alexander Leidinger wrote:
> > On Sat, 30 Aug 2003 10:41:02 -0400 (EDT)
> > Robert Watson <rwatson@freebsd.org> wrote:
> >
> >
> >>mind. The other thing we should encourage developers to do more is use
> >>code coverage tools -- phk recently pointed me at kernbb(8) as a way to
> >>feed gcov(1).
> >
> >
> > Documenting the various tools and how to use them on FreeBSD would be a
> > nice start. Maybe the interested parties can come up with a list of
> > programs and maybe a short introduction what those tools do/provide and
> > a link to documentation and hand them over to the doc people...
>
> A section 7 man page? Also, it would be nice if intro(7) had an index to
> the man pages in this section. Of course, getting people to write about
> the existing tools and their usage is the hardest part...
As I don't think this should be limited to base system tools: no, IMO a
book or article would fit better (I'm sure our doc team is willing to
help with the markup if someone delivers content).
Bye,
Alexander.
--
0 and 1. Now what could be so hard about that?
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030905152847.2571f544.Alexander>