diff options
| author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2019-05-01 16:53:05 +0300 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2019-05-28 20:29:07 +0300 |
| commit | b1954bbf1272e64a68aef745b10e2380ad84be01 (patch) | |
| tree | d4c16ee51f018dbc16520f4b6f04516ef3f4557f /certs | |
| parent | cd6c84d8f0cdc911df435bb075ba22ce3c605b07 (diff) | |
| download | linux-b1954bbf1272e64a68aef745b10e2380ad84be01.tar.xz | |
ACPI: tools: Exclude tools/* from .gitignore patterns
tools/power/acpi/.gitignore has the following entries:
acpidbg
acpidump
ec
They are intended to ignore the following build artifacts:
tools/power/acpi/acpidbg
tools/power/acpi/acpidump
tools/power/acpi/ec
However, those .gitignore entries are effective not only for the
current directory, but also for any sub-directories.
So, from the point of .gitignore grammar, the following check-in
directories are also considered to be ignored:
tools/power/acpi/tools/acpidbg
tools/power/acpi/tools/acpidump
tools/power/acpi/tools/ec
As the manual gitignore(5) says "Files already tracked by Git are not
affected", this is not a problem as far as Git is concerned.
However, Git is not the only program that parses .gitignore because
.gitignore is useful to distinguish build artifacts from source files.
For example, tar(1) supports the --exclude-vcs-ignore option. As of
writing, this option does not work perfectly, but it intends to create
a tarball excluding files specified by .gitignore.
The issue can be prevented by prefixing the pattern with a slash; the
leading slash means the specified pattern is relative to the current
directory.
Do that for the "include" directory too for consistency and extra
safety.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
[ rjw: Subject & changelog ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions