aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* CODING_STYLE: clarify that we really should use O_CLOEXEC everywhereLennart Poettering2014-10-301-0/+5
|
* CODING_STYLE: don't clobber arguments on failureLennart Poettering2014-10-271-1/+5
|
* CODING_STYLE: clarify that single-line if blocks should not be enclosed in {}Lennart Poettering2014-10-221-2/+13
|
* Fix a few more typosRuben Kerkhof2014-08-301-1/+1
|
* CODING_STYLE: document that we don't break lines at 80chLennart Poettering2014-08-211-1/+4
|
* Unify parse_argv styleZbigniew Jędrzejewski-Szmek2014-08-031-0/+5
| | | | | | | | | | | | | | | | getopt is usually good at printing out a nice error message when commandline options are invalid. It distinguishes between an unknown option and a known option with a missing arg. It is better to let it do its job and not use opterr=0 unless we actually want to suppress messages. So remove opterr=0 in the few places where it wasn't really useful. When an error in options is encountered, we should not print a lengthy help() and overwhelm the user, when we know precisely what is wrong with the commandline. In addition, since help() prints to stdout, it should not be used except when requested with -h or --help. Also, simplify things here and there.
* doc: use expanded forms for written styleJan Engelhardt2014-06-281-12/+12
|
* doc: typographical improvements and choice of wordsJan Engelhardt2014-06-281-5/+5
|
* doc: grammatical correctionsJan Engelhardt2014-06-281-12/+12
|
* Fix several small typosJonathan Boulle2014-05-241-1/+1
|
* extend CODING_STYLE document a bitLennart Poettering2013-12-091-17/+63
|
* trivial coding style clean upsThomas Hindoe Paaboel Andersen2013-12-031-1/+1
| | | | | | | | | | | | | | - Add space between if/for and the opening parentheses - Place the opening brace on same line as the function (not for udev) From the CODING_STYLE Try to use this: void foo() { } instead of this: void foo() { }
* analyze: various cleanupsLennart Poettering2013-03-081-9/+105
| | | | | | | | | | | | | | | | | | Update systemd-analyze to follow the coding style of the other tools more closely. Also, update the CODING_STYLE to document this for future additions. Changes: - Always use usec_t for time units, so that we always use the same types everywhere, and format times the same way as everywhere else. - Add "static" to global variables - Make sure we can always distuingish OOM and other errors: ensure we always return useful error codes from all functions. - Always free unit_times array
* Clarify sentenceTollef Fog Heen2013-01-291-1/+1
|
* Minor typoTollef Fog Heen2012-10-011-1/+1
|
* Be consistent about "." vs no "." at the end of lines"Tollef Fog Heen2012-10-011-4/+4
|
* Spelling CorrectionsHarald Hoyer2011-02-281-1/+1
| | | | Just some lame spelling corrections with no functionality.
* CODING_STYLE: minor updatesLennart Poettering2010-02-141-0/+11
|
* CODING_STYLE: add missing -Lennart Poettering2009-11-181-1/+1
|
* initial commitLennart Poettering2009-11-181-0/+16