summaryrefslogtreecommitdiff
path: root/tools/find-double-newline.sh
Commit message (Collapse)AuthorAgeFilesLines
* tools: shellcheck-ify most of the tool scriptsFrantisek Sumsal2021-04-201-9/+11
|
* license: LGPL-2.1+ -> LGPL-2.1-or-laterYu Watanabe2020-11-091-1/+1
|
* scripts: use 4 space indentationZbigniew Jędrzejewski-Szmek2019-04-121-35/+34
| | | | | | | | | | | | | | | | | | We had all kinds of indentation: 2 sp, 3 sp, 4 sp, 8 sp, and mixed. 4 sp was the most common, in particular the majority of scripts under test/ used that. Let's standarize on 4 sp, because many commandlines are long and there's a lot of nesting, and with 8sp indentation less stuff fits. 4 sp also seems to be the default indentation, so this will make it less likely that people will mess up if they don't load the editor config. (I think people often use vi, and vi has no support to load project-wide configuration automatically. We distribute a .vimrc file, but it is not loaded by default, and even the instructions in it seem to discourage its use for security reasons.) Also remove the few vim config lines that were left. We should either have them on all files, or none. Also remove some strange stuff like '#!/bin/env bash', yikes.
* tools: make various scripts find the top-levle git dir automaticallyLennart Poettering2018-06-071-2/+4
|
* find-double-newline: look in headers tooLennart Poettering2018-05-221-2/+2
|
* tree-wide: drop spurious newlines (#8764)Lennart Poettering2018-04-191-0/+40
Double newlines (i.e. one empty lines) are great to structure code. But let's avoid triple newlines (i.e. two empty lines), quadruple newlines, quintuple newlines, …, that's just spurious whitespace. It's an easy way to drop 121 lines of code, and keeps the coding style of our sources a bit tigther.