~lukeshu/systemd - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2015-06-11	build-sys: split internal basic/ library from shared/	Kay Sievers
	basic/ can be used by everything cannot use anything outside of basic/ libsystemd/ can use basic/ cannot use shared/ shared/ can use libsystemd/
2015-04-11	shared: move replace_env* from util to env-util	Ronny Chevalier

2015-02-23	remove unused includes	Thomas Hindoe Paaboel Andersen
	This patch removes includes that are not used. The removals were found with include-what-you-use which checks if any of the symbols from a header is in use.
2015-02-12	Add missing includes in header files	Thomas Hindoe Paaboel Andersen
	This fixes various issues found by globally reordering the include sections of all .c files.
2014-12-23	env-util: don't include files from src/core/	Lennart Poettering

2014-10-17	environment: append unit_id to error messages regarding EnvironmentFile	Lukas Nykryn

2014-01-12	core: clean up environment block for --user instances a bit	Lennart Poettering

2013-05-02	Add __attribute__((const, pure, format)) in various places	Zbigniew Jędrzejewski-Szmek
	I'm assuming that it's fine if a _const_ or _pure_ function calls assert. It is assumed that the assert won't trigger, and even if it does, it can only trigger on the first call with a given set of parameters, and we don't care if the compiler moves the order of calls.
2013-04-17	core/execute: report invalid environment variables from files	Harald Hoyer
	Because "export key=val" is not supported by systemd, an error is logged where the invalid assignment is coming from. Introduce strv_env_clean_log() to log invalid environment assignments, where logging is possible and allowed. parse_env_file_internal() is modified to allow WHITESPACE in keys, to report the issues later on.
2013-02-11	manager: validate environment parameters for SetEnvironment(), ↵	Lennart Poettering
	UnsetEnvironment() bus calls
2013-02-11	env: considerably beef up environment cleaning logic	Lennart Poettering
	Now, actually check if the environment variable names and values used are valid, before accepting them. With this in place are at some places more rigid than POSIX, and less rigid at others. For example, this code allows lower-case environment variables (which POSIX suggests not to use), but it will not allow non-UTF8 variable values. All in all this should be a good middle ground of what to allow and what not to allow as environment variables. (This also splits out all environment related calls into env-util.[ch])