[kernel] r4771 - people/dannf/patchinfo

[Dann Frazier]

Author: dannf
Date: Thu Nov 10 05:39:03 2005
New Revision: 4771

Added:
   people/dannf/patchinfo/00example
      - copied, changed from r4770, people/dannf/patchinfo/00boilerplate
Modified:
   people/dannf/patchinfo/00boilerplate
Log:
create a real boilerplate & move all teh sample stuff to an example file


Modified: people/dannf/patchinfo/00boilerplate
==============================================================================
--- people/dannf/patchinfo/00boilerplate	(original)
+++ people/dannf/patchinfo/00boilerplate	Thu Nov 10 05:39:03 2005
@@ -1,33 +1,9 @@
-## Lines beginning with '##' are just for this boilerplate - they shouldn't be
-## transferred to patch track files
-## A list of valid fields for patch description files, with examples
-Candidate: ##NEEDED## | CAN/CVE-XXXX-XXXX | N/A
+Candidate:
 References:
- CONFIRM:##URL##
- MISC:##URL## 
 Description: 
- Summary of the issue
- .
- Might be used for requesting a CVE, or included in a DSA
 Notes:
- Notes for internal use by the kernel team
-Bug: 123456, 123457
-## per-tree status.
-##  pending: fix has been committed to svn
-##  released: we've cut a version with this fix in it
-##  needed: bug is applicable to this tree and needs a fix
-##  An empty value means that someone needs to determine the relevancy for this tree
-## 
-##
-## status maybe followed by a version string in ()'s, and/or a patchname in []'s
-## Prerequisite patches maybe listed in [] as well, even though they may not be
-## directly part of the fix.
-upstream: released (2.6.12, 2.4.29-rc3), pending (2.6.11.3)
-2.6.13: pending
-2.6.12: pending (2.6.12-9)
+Bugs:
+upstream:
+2.6.14: pending
 2.6.8-sarge-security: released (2.6.8-16sarge1) [patchname.patch, prerequisite.dpatch, prerequisite2.dpatch]
 2.4.27-sarge-security: needed
-2.4.27: N/A
-
-
-## Should released tag be renamed to fixed?

Copied: people/dannf/patchinfo/00example (from r4770, people/dannf/patchinfo/00boilerplate)
==============================================================================
--- people/dannf/patchinfo/00boilerplate	(original)
+++ people/dannf/patchinfo/00example	Thu Nov 10 05:39:03 2005
@@ -1,4 +1,4 @@
-## Lines beginning with '##' are just for this boilerplate - they shouldn't be
+## Lines beginning with '##' are just for this example - they shouldn't be
 ## transferred to patch track files
 ## A list of valid fields for patch description files, with examples
 Candidate: ##NEEDED## | CAN/CVE-XXXX-XXXX | N/A
@@ -11,7 +11,7 @@
  Might be used for requesting a CVE, or included in a DSA
 Notes:
  Notes for internal use by the kernel team
-Bug: 123456, 123457
+Bugs: 123456, 123457
 ## per-tree status.
 ##  pending: fix has been committed to svn
 ##  released: we've cut a version with this fix in it
@@ -28,6 +28,3 @@
 2.6.8-sarge-security: released (2.6.8-16sarge1) [patchname.patch, prerequisite.dpatch, prerequisite2.dpatch]
 2.4.27-sarge-security: needed
 2.4.27: N/A
-
-
-## Should released tag be renamed to fixed?