systemd - systemd

	Commit message (Collapse)	Author	Age	Files	Lines
*	scripts: use 4 space indentation	Zbigniew Jędrzejewski-Szmek	2019-04-12	1	-0/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	editorconfig: add rule for meson.build files (#6671)	Felipe Sateler	2017-08-28	1	-0/+4
\|
*	editors: only extend line width to 119 for C and XML files	Lennart Poettering	2016-02-10	1	-2/+5
\| \| \| \| \| \| \| \| \| \| \| \|	For all other files leave the line width at 79 as before. This is a good idea since we generally don't want text files such as catalog files, unit files or README/NEWS files to be line-broken at 119 since they are regularly browsed on text terminals. While we are at it, also add a couple of comments to the various files. (Note that .editorconfig doesn't carry line-width information, simply because the specification doesn't know the concept.)
*	add editorconfig configuration	Christian Hesse	2015-11-23	1	-0/+17
	We want indention with spaces, so specify in editorconfig. http://editorconfig.org/