> > > And as to the author: Writing docu while you are implementing something
> > > might work in a commercial environment where you want to be able to
> > > market something before it's sell-by date, but for hobbiests who
> > > basically spend the odd evening doing something, it is too much hassle.
> >
> > In case FreeBSD wants to enter commercial environments, we have to behave
> > like behaving in commercial environments.
>
> Ok, so let's follow Microsoft's industry-leading documentation standards.
That remark is content-free for all of us who never read MS
documentation.
--
Greg Black -- <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
Fight censorship in Australia: <http://www.efa.org.au>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
