rename the active issues directory from 'patch-tracking' to the more accurate 'active'

git-svn-id: svn+ssh://svn.debian.org/svn/kernel-sec@549 e094ebfe-e918-0410-adfb-c712417f3574

1 files changed, 35 insertions, 0 deletions

diff --git a/active/00example b/active/00example
new file mode 100644
index 000000000..914b13c03
--- /dev/null
+++ b/active/00example
@@ -0,0 +1,35 @@
+## 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: requested | needed | CAN/CVE-XXXX-XXXX | N/A
+## See: http://cve.mitre.org/cve/refs/refkey.html for mitre's reference key to
+## when adding to the References field
+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
+Bugs: 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
+##  ignored: bug maybe applicable, but we're currently ignoring it - perhaps
+##           its too difficult to backport, or we think its a non-issue.
+##           justification should be noted in the "Notes" field
+##  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)
+linux-2.6: pending (2.6.12-9)
+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
+2.4.18-woody-security: ignored