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.
--Ted
_______________________________________________
OpenAFS-devel mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-devel
- Re: [OpenAFS-devel] @sys as list patch in CVS Derek Atkins
- RE: [OpenAFS-devel] @sys as list patch in CVS Neulinger, Nathan
- Re: [OpenAFS-devel] @sys as list patch in CVS Sam Hartman
- Re: [OpenAFS-devel] @sys as list patch in CVS Derrick J Brashear
- Re: [OpenAFS-devel] @sys as list patch in CVS Derrick J Brashear
- Re: [OpenAFS-devel] @sys as list patch in CVS Sam Hartman
- Re: [OpenAFS-devel] @sys as list patch in CVS Derrick J Brashear
- Re: [OpenAFS-devel] @sys as list patch in CVS Sam Hartman
- Re: [OpenAFS-devel] @sys as list patch in CVS Derrick J Brashear
- Re: [OpenAFS-devel] @sys as list patch in CVS Ted McCabe
- Re: [OpenAFS-devel] @sys as list patch in CVS John Berninger
- Re: [OpenAFS-devel] @sys as list patch in CVS Sam Hartman
- RE: [OpenAFS-devel] @sys as list patch in CVS Neulinger, Nathan
- RE: [OpenAFS-devel] @sys as list patch in CVS Derrick J Brashear
- RE: [OpenAFS-devel] @sys as list patch in CVS Neulinger, Nathan
- RE: [OpenAFS-devel] @sys as list patch in CVS Neulinger, Nathan
- Re: [OpenAFS-devel] @sys as list patch in CVS Erik J Burckart
- Re: [OpenAFS-devel] @sys as list patch in CVS Derrick J Brashear
