Jason Edgecombe <[EMAIL PROTECTED]> wrote: > Russ Allbery wrote: >> Russ Allbery <[EMAIL PROTECTED]> writes: >>> Basically, please feel free to pick any of the documentation and >>> just let me know what you're working on. As you finish >>> modifications, the easiest way for me to process those changes is >>> as unified diffs, but if you want to send a complete replacement >>> file, I can deal with that as well. Please submit any >>> modifications as bugs to openafs-bugs at openafs.org, and please >>> either copy me on the message or let me know the RT number after >>> the bug has been submitted since I don't always track all the bugs. >> >> Oh, and forgot to mention: Please work against the current CVS head >> if at all possible. You can find instructions on how to check out >> the current development version of OpenAFS from anonymous CVS at >> www.openafs.org; see CVS information in the sidebar. >> >> Please do ask if you have any questions about how to make that work. > > I'll poke around and see what I feel like working on.
Is the openafs-doc list being actively used? There don't seem to have been any posts since Feb 2006. https://lists.openafs.org/mailman/listinfo/openafs-doc I would imagine that anyone working on documentation should be on this list. But perhaps I mis-understand its purpose. <<CDC _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
