[OpenAFS-devel] @sys as list patch in CVS

[Sam Hartman]

>>>>> "John" == John Berninger <John_Berninger@ncsu.edu> writes:

    John> On Tue, 05 Jun 2001, Ted McCabe wrote:
    >> At 1:37 PM -0400 6/5/01, Sam Hartman wrote: >...<snip> >I
    >> suggest that for future patches, >you require an entry in that
    >> file for new functionality.
    >> 
    >> Makes good sense.  It does seem to raise another issue, namely
    >> documenting patch submission: preferred method thereof,
    >> requirements, tools, etc.

    John> This may or may not be related to other documentation
    John> issues, but might I suggest a decision be made regarding
    John> what form(s) of documentation will be provided to end users
    John> / administrators / others in need of documentation, then
    John> decide what would be easiest to produce that / those forms?

We find ourselves in an annoying position.  We do not have source
other than the pdfs for the manuals.  This makes your suggestion
somewhat impractical.  Certainly if you are volunteering to convert
the existing manuals from pdf to docbook, this sounds like a great
idea.