diff options
| author |  Johannes Schindelin <johannes.schindelin@gmx.de> | 2019-09-05 04:16:33 -0700 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2019-09-05 10:46:55 -0700 |
| commit | aac6ff7b5beeea9bca66ecda6eec60fc1dd447ec (patch) | |
| tree | 0b5ca0f7a972662171854709eaeca83368435ca9 /Documentation/RelNotes/1.6.2.1.txt | |
| parent | git: avoid calling aliased builtins via their dashed form (diff) | |
| download | tgif-aac6ff7b5beeea9bca66ecda6eec60fc1dd447ec.tar.xz | |
.gitignore: stop ignoring `.manifest` files
On Windows, it is possible to embed additional metadata into an
executable by linking in a "manifest", i.e. an XML document that
describes capabilities and requirements (such as minimum or maximum
Windows version). These XML documents are expected to be stored in
`.manifest` files.
At least _some_ Visual Studio versions auto-generate `.manifest` files
when none is specified explicitly, therefore we used to ask Git to
ignore them.
However, we do have a beautiful `.manifest` file now:
`compat/win32/git.manifest`, so neither does Visual Studio auto-generate
a manifest for us, nor do we want Git to ignore the `.manifest` files
anymore.
Further reading on auto-generated `.manifest` files:
https://docs.microsoft.com/en-us/cpp/build/manifest-generation-in-visual-studio
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/RelNotes/1.6.2.1.txt')
0 files changed, 0 insertions, 0 deletions