Date: Mon, 17 Apr 1995 19:31:28 -0700 (PDT) From: Julian Elischer <julian@ref.tfs.com> To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Cc: jkh@thud.cdrom.com, CVS-commiters@thud.cdrom.com, cvs-usrsbin@thud.cdrom.com Subject: Re: cvs commit: src/usr.sbin/xten README Makefile Install.notes Message-ID: <199504180231.TAA00788@ref.tfs.com> In-Reply-To: <199504180157.SAA10788@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 17, 95 06:57:16 pm
next in thread | previous in thread | raw e-mail | index | archive | help
>
> >
> > jkh 95/04/17 18:57:52
> >
> > Modified: usr.sbin/xten Makefile
> > Added: usr.sbin/xten README
> > Removed: usr.sbin/xten Install.notes
> > Log:
> > Extensive updates to this package.
> > Moved Install.notes -> README, as ratified at the core meeting of
> > April 13th.
>
> Which I find no mention of in the Minutes posted to the list :-(, what
> else has not been mentioned???
hmmm I thought that I did mention it...
(I'll go look afterwards)
Actually maybe we miscommunicated....
I thought we were only talking about allowing documantation WITHIN
the kernel tree, and I think I mentionned it in the minutes
in that light.. (e.g. if you look in most kernel trees you find NO
documentation..)
I thought what we agreed to was:
allow, no, in fact, possitively approve of, README
files scattered through teh kernel source tree, documenting interfaces
and configuration options etc.. all labelled appropriatly
as README or README.{driver-x}
What happens outside the kernel is basically up to whoever
writes the code, I thought.
>
>
> --
> Rod Grimes rgrimes@gndrsh.aac.dev.com
> Accurate Automation Company Custom computers for FreeBSD
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504180231.TAA00788>