| .. | .. |
|---|
| 32 | 32 | layout of the files below for details on how to do this.) |
|---|
| 33 | 33 | |
|---|
| 34 | 34 | obsolete/ |
|---|
| 35 | | - This directory documents interfaces that are still remaining in |
|---|
| 35 | + This directory documents interfaces that are still remaining in |
|---|
| 36 | 36 | the kernel, but are marked to be removed at some later point in |
|---|
| 37 | 37 | time. The description of the interface will document the reason |
|---|
| 38 | 38 | why it is obsolete and when it can be expected to be removed. |
|---|
| .. | .. |
|---|
| 58 | 58 | be changed further. |
|---|
| 59 | 59 | |
|---|
| 60 | 60 | |
|---|
| 61 | +Note: |
|---|
| 62 | + The fields should be use a simple notation, compatible with ReST markup. |
|---|
| 63 | + Also, the file **should not** have a top-level index, like:: |
|---|
| 64 | + |
|---|
| 65 | + === |
|---|
| 66 | + foo |
|---|
| 67 | + === |
|---|
| 68 | + |
|---|
| 61 | 69 | How things move between levels: |
|---|
| 62 | 70 | |
|---|
| 63 | 71 | Interfaces in stable may move to obsolete, as long as the proper |
|---|