On Windows, when `core.symlinks` is `false` or unset (since itdefaults to `false` on Windows), Git checks out symbolic links asregular files whose contents are symlinks' target paths. Modifyingthose regular files and committing the changes alters the symlinktarget in the repository, and when they are checked out as actualsymlinks, the targets are different.But the `end-of-file-fixer` pre-commit hook automatically addsnewlines to the end of regular files that lack them. It doesn't dothis on actual symlinks, but it does do it to regular files thatstand in for symlinks. This causes it to carry a risk of breakingsymlinks if it is run on Windows and the changes committed, and itis easy to miss that this will happen because `git diff` outputshows it the same way as other additions of absent newlines.This deliberately commits the change that end-of-file-fixer makesto the `LICENSE-BSD` symlink, in order to allow a mitigation beyondjust excluding that symlink (or replacing it with a regular file)to be tested. This change must be undone, of course.

Rationale:- Small but likely benefit in general, since there are no currently  foreseen intentional use cases of committing of broken/dangling  symlinks in this project. So such symlinks that arise are likely  unintentional.- If the end-of-file-fixer hook has run on a Windows system where  `core.symlinks` has *not* been set to `true`, and symlinks' paths  have not been excluded, then a newline character is added to the  end of the path held in the regular file Git checks out to stand  in for the symlink. Because it is not actually a symlink, this  will not detect the problem at that time (regardless of the order  in which this and that hook run relative to each other). But when  it is then run on CI on a system where symlinks are checked out,  it will detect the problem.

This reverts commitbdfa280.

The unanchored `LICENSE` and `COPYING` alternatives match thepattern anywhere, and therefore exclude the currently used path`fuzzing/LICENSE-BSD`.License files are more likely than other files in this project tobe introduced as symlinks, and less likely to be noticedimmediately if they break. Symlinks can be checked out as regularfiles when `core.symlinks` is set to `false`, which is rare outsideof Windows but is the default behavior when unset on Windows.This exclusion fixes the current problem that end-of-file-fixerbreaks those links by adding a newline character to the end (thesymlinks are checked out broken if that is committed). It alsoguards against most future cases involving licenses, thoughpossibly not all, and not other unrelated cases where symlinks maybe used for other purposes.Although the pre-commit-hooks repository also provides adestroyed-symlinks hook that detects the situation of a symlinkthat has been replaced by a regular file, this does not add thathook, because this situation is not inherently a problem. The codehere does not require symlinks to be checked out to work, andadding that would break significant uses of the repository onWindows.Note that this leaves the situation where a license file may be asymlink to another license file and may thus be checked out as aregular file containing that file's path. However, it is easy tounderstand that situation and manually follow the path. Thatdiffers from the scenario where a symlink is created but broken,because attempting to open it gives an error, and the error messageis often non-obvious, reporting that a file is not found but givingthe name of the symlink rather than its target.

Byron left a comment