Just noticed Documentation/video-output.txt in 2.6.21-rc. Add note about it.
[linux-2.6/linux-acpi-2.6/ibm-acpi-2.6.git] / README
blob6392d755b60b9f9f0d5f95e33af76a659c8c50c8
1 ibm-acpi development tree
2 =========================
4 This tree is an staging and archival area for ibm-acpi patches and
5 documentation.
7 releases/: archival area
9 releases/upstream/:  directory containing the patches in public releases
10         of ibm-acpi
12 releases/upstream/sunrise/: reference (base) version of ibm-acpi
14 rejected/: staging area for rejected/superseeded/abandoned patches
16 queues/: various staging areas
17 queues/acpi-test/: staging area with patches that made it to acpi-test
18 queues/ibm-acpi/: staging area with patches from ibm-acpi development
19 queues/for-upstream/: staging area with patches being submitted upstream
22 sf.net/: Files for ibm-acpi.sf.net
24 ibm-acpi git tree
25 =================
27 Branch                  Description
28 ------                  ---------------------------------------------
29 master                  ibm-acpi development tree, see above.
31 release/*               ibm-acpi releases for various kernels.
33 for-upstream/
34         mm              ibm-acpi patches queued to be added to -mm tree,
35                         for please pull requests to Andrew.
37         acpi-test       ibm-acpi patches queued to be added to Len's
38                         acpi-test tree, for please pull requests to Len.
39                         This is the normal submission path upstream.
41         acpi-release    ibm-acpi patches queued to be added to mainline
42                         (through Len's acpi-release tree), for please
43                         pull requests to Len.  Rarely used.
45 upstream/*              various upstream trees.
47 queue/                  patch queue for the next ibm-acpi release
48   already-upstream      patches already merged upstream (acpi-test),
49                         patches are removed when they hit mainline or
50                         a sourceforge release is made.
52   waiting               patches waiting to be sent or merged upstream.
54 devel                   Current work (not yet complete or stable)
57 Typical patch flow:
58         hmh -> Len (acpi-test) -> mm -> Len (acpi-release) -> Linus
60 When in doubt, ask ibm-acpi-devel@lists.sourceforge.net.
62 Bug reports, comments, new patches, etc are welcome at
63 ibm-acpi-devel@lists.sourceforge.net.
65 Contact me directly at ibm-acpi@hmh.eng.br.
67 -- Henrique de Moraes Holschuh <hmh@hmh.eng.br>