elogind - Debian dgit repo for package elogind

	Commit message (Collapse)	Author	Age
*	Prep v233: Update root build files to upstream version	Sven Eden	2017-07-17
\|
*	Prep v231: Update build root files to upstream	Sven Eden	2017-06-16
\|
*	Prep v230: Apply missing upstream fixes and updates (1/8) root build files.	Sven Eden	2017-06-16
\|
*	Prep v229: Update core build files to upstream	Sven Eden	2017-05-17
\|
*	Prep v228: Update base files to upstream version.	Sven Eden	2017-04-26
\|
*	Update Build files	Sven Eden	2017-03-29
\|
*	Prep v226: Sync build files with upstream	Sven Eden	2017-03-14
\|
*	Prep v225: Sync build files with upstream	Sven Eden	2017-03-14
\|
*	Prep v221: Update and clean up build system to sync with upstream	Sven Eden	2017-03-14
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	This commit replays the moving around of source files that have been done between systemd-219 and systemd-221. Further the Makefile.am is synchronized with the upstream version and then "re-cleaned". A lot of functions, that are not used anywhere in elogind have been coated into #if 0/#endif directives to further shorten the list of dependencies. All unneeded files have been removed.
*	Merge remaining elogind/master root files of the systemd upstream tag 'v220'	Sven Eden	2017-03-14
\|
*	CODING_STYLE: mention that dup() should not be used	Lennart Poettering	2015-04-03
\|
*	CODING_STYLE: clarify that exit() is never OK to call	Lennart Poettering	2015-04-02
\|
*	CODING_STYLE: mention casting of function invocations to (void)	Lennart Poettering	2015-03-10
\|
*	update TODO	Lennart Poettering	2015-02-28
\|
*	tree-wide: whenever we include libgen.h, immediately undefine basename()	Lennart Poettering	2015-02-11
\| \| \| \|	Also, document in adjacent comments and in CODING_STYLE why we do that.
*	CODING_STYLE: elaborate on O_CLOEXEC a bit	Lennart Poettering	2015-02-10
\|
*	Reindent man pages to 2ch	Zbigniew Jędrzejewski-Szmek	2015-02-03
\|
*	CODING_STYLE: clarify that we really should use O_CLOEXEC everywhere	Lennart Poettering	2014-10-30
\|
*	CODING_STYLE: don't clobber arguments on failure	Lennart Poettering	2014-10-27
\|
*	CODING_STYLE: clarify that single-line if blocks should not be enclosed in {}	Lennart Poettering	2014-10-22
\|
*	Fix a few more typos	Ruben Kerkhof	2014-08-30
\|
*	CODING_STYLE: document that we don't break lines at 80ch	Lennart Poettering	2014-08-21
\|
*	Unify parse_argv style	Zbigniew Jędrzejewski-Szmek	2014-08-03
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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 style	Jan Engelhardt	2014-06-28
\|
*	doc: typographical improvements and choice of words	Jan Engelhardt	2014-06-28
\|
*	doc: grammatical corrections	Jan Engelhardt	2014-06-28
\|
*	Fix several small typos	Jonathan Boulle	2014-05-24
\|
*	extend CODING_STYLE document a bit	Lennart Poettering	2013-12-09
\|
*	trivial coding style clean ups	Thomas Hindoe Paaboel Andersen	2013-12-03
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	- 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 cleanups	Lennart Poettering	2013-03-08
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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 sentence	Tollef Fog Heen	2013-01-29
\|
*	Minor typo	Tollef Fog Heen	2012-10-01
\|
*	Be consistent about "." vs no "." at the end of lines"	Tollef Fog Heen	2012-10-01
\|
*	Spelling Corrections	Harald Hoyer	2011-02-28
\| \| \| \|	Just some lame spelling corrections with no functionality.
*	CODING_STYLE: minor updates	Lennart Poettering	2010-02-14
\|
*	CODING_STYLE: add missing -	Lennart Poettering	2009-11-18
\|
*	initial commit	Lennart Poettering	2009-11-18