The DSF Examples contains some commented out source that is enabled
via a script so this commit cleans that up for new formatting rules.
Change-Id: I82c5e195cc3746415c659b2c0fc72b8118cdc56c
The previous alignment of all the warnings/ignores
led to too many warnings that weren't there before. This
commit relaxes them a bit.
The core/org.eclipse.cdt.core/.settings/org.eclipse.jdt.core.prefs
is still the "master" copy, with
releng/scripts/check_code_cleanliness.sh containing the
exceptions that apply to test plug-ins.
Change-Id: Ibd4e31ade0b42b31e7cbe5a94f06c6fc15183a56
git ls-files has two benefits:
- Only finds tracked files
This is necessary because we were having a few cleanups
being attempted on ignored files.
- Is much faster
Change-Id: I5a53497f8ef9c839676b7ef7e3be35171140f4b9
This commit contains the formatter settings and compiler settings,
using org.eclipse.cdt.core as the master for .settings and
a script to copy them to all the other projects with
apply_jdt_prefs_to_all_projects.sh
Change-Id: Ifd1a45879bed716273cae0ea05b55f629210c36e
Script based on work done by Lars Vogel on Eclipse Platform.
See https://git.eclipse.org/r/#/c/127598/
Change-Id: Ic8d04a20c955179645fdeeb11cb3861d7b31fa3f
There is also a new script to verify completeness of .gitattributes:
releng/scripts/verify_gitattributes.sh
Change-Id: I2ce270852ab54b66b6c474a6ec94203fe5bba78b
The script is quite basic. It does not even take parameters.
However, considering it will be run probably once every three
years, I felt it was sufficient.
Change-Id: Ic2b533758529f393d6e37c010f0a5cb666e84b53
