]> git.baikalelectronics.ru Git - kernel.git/commit
ACPI: tools: Exclude tools/* from .gitignore patterns
authorMasahiro Yamada <yamada.masahiro@socionext.com>
Wed, 1 May 2019 13:53:05 +0000 (22:53 +0900)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Tue, 28 May 2019 17:29:07 +0000 (19:29 +0200)
commit0eb6a9f789606f970831f66b7fcab6acab5aac0c
treed4c16ee51f018dbc16520f4b6f04516ef3f4557f
parent7f3e30282b380958e65348f1509b90f11030d416
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>
tools/power/acpi/.gitignore