| 1 |
## A list of valid fields for patch description files, with examples
|
| 2 |
Candidate: ##NEEDED## | CAN/CVE-XXXX-XXXX | N/A
|
| 3 |
References:
|
| 4 |
CONFIRM:##URL##
|
| 5 |
MISC:##URL##
|
| 6 |
Description:
|
| 7 |
Summary of the issue
|
| 8 |
.
|
| 9 |
Might be used for requesting a CVE, or included in a DSA
|
| 10 |
Notes:
|
| 11 |
Notes for internal use by the kernel team
|
| 12 |
Bug: 123456, 123457
|
| 13 |
## per-tree status.
|
| 14 |
## pending: fix has been committed to svn
|
| 15 |
## released: we've cut a version with this fix in it
|
| 16 |
## needed: bug is applicable to this tree and needs a fix
|
| 17 |
## An empty value means that someone needs to determine the relevancy for this tree
|
| 18 |
##
|
| 19 |
##
|
| 20 |
## status maybe followed by a version string in ()'s, and/or a patchname in []'s
|
| 21 |
## Prerequisite patches maybe listed in [] as well, even though they may not be
|
| 22 |
## directly part of the fix.
|
| 23 |
upstream: released (2.6.12, 2.4.29-rc3), pending (2.6.11.3)
|
| 24 |
2.6.13: pending
|
| 25 |
2.6.12: pending (2.6.12-9)
|
| 26 |
2.6.8-sarge-security: released (2.6.8-16sarge1) [patchname.patch, prerequisite.dpatch, prerequisite2.dpatch]
|
| 27 |
2.4.27-sarge-security: needed
|
| 28 |
2.4.27: N/A
|
| 29 |
|
| 30 |
|
| 31 |
## Should released tag be renamed to fixed?
|
Parent Directory
| 
Revision Log