Opened 16 years ago
Closed 13 years ago
#380 closed task (fixed)
Move include files delivered with Intel ACPICA sources to src\acpi\intel\include
Reported by: | Steven Levine | Owned by: | David Azarewicz |
---|---|---|---|
Priority: | major | Milestone: | Release version 3.19 |
Component: | Intel ACPICA | Version: | 3.14 |
Keywords: | Cc: |
Description
Currently, the acpi\src\common\include contains a mixture of files delivered with the Intel ACPICA sources and platform specific files we maintain. This makes integrating new ACPICA distributions more difficult that need be. It also makes the ACPI sources harder to understand.
The Intel supplied files should move to acpi\src\intel\include. This corresponds the the directory structure that Intel distributes.
The svn commands to move the files are simple.
The makefile changes to support the additional directory are simple.
Change History (6)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Yes I know all this and I know how to implement these kinds of things. I've done them many times before.
Note, the ticket is assigned to me. If you want to contribute ideas that will make it easier for me to implement the changes, fine. Otherwise, I recommend you don't tell me what I can't do. I prefer to take the positive approach and assume that solutions are always available. It might take some time, but the solution will come.
follow-up: 4 comment:3 by , 16 years ago
now all directory for acpi ca is at 2005 acpi ca build. "Include" don't be only one, which not compared with current acpi ca. Note. Iasl must be in intel too ;-)
comment:4 by , 16 years ago
now all directory for acpi ca is at 2005 acpi ca build. "Include" don't be only one, which not compared with current acpi ca. Note. Iasl must be in intel too ;-)
Why the smiley? I understand all this. Subversion can handle moving these files about a will retain the complete change history. If you checkout a changeset with the old structure is will look just like it did when the submitted the changeset. How well to do you understand what svn can do?
Note that this ticket is assigned to me. If you want to assist positively, I will welcome your assistance. If you are going to try to tell me how hard it will be, don't bother.
Note also that this ticket is assigned to milestone 3.16. We have plenty of work to do to get a stable 3.15 out the door and that's where we should concentrate our efforts.
comment:5 by , 13 years ago
Owner: | changed from | to
---|
comment:6 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
And do this with every change from acpi ca include path? BTW. Do you know, that command line is ending size?