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

Age	Commit message (Collapse)	Author
2016-02-22	tree-wide: make ++/-- usage consistent WRT spacing	Vito Caputo
	Throughout the tree there's spurious use of spaces separating ++ and -- operators from their respective operands. Make ++ and -- operator consistent with the majority of existing uses; discard the spaces.
2016-02-10	tree-wide: remove Emacs lines from all files	Daniel Mack
	This should be handled fine now by .dir-locals.el, so need to carry that stuff in every file.
2016-01-27	utf8.[ch] et al: use char32_t and char16_t instead of int, int32_t, int16_t	Shawn Landden
	rework C11 utf8.[ch] to use char32_t instead of uint32_t when referring to unicode chars, to make things more expressive. [ @zonque: * rebased to current master * use AC_CHECK_DECLS to detect availibility of char{16,32}_t * make utf8_encoded_to_unichar() return int ]
2016-01-13	basic: add ascii_strcasecmp_nn() call	Lennart Poettering
	In contrast to ascii_strcasecmp_nn() it takes two character buffers with their individual length. It will then compare the buffers up the smaller size of the two buffers, and finally the length themselves.
2016-01-13	basic: add new ascii_strcasecmp_n() call	Lennart Poettering

2016-01-11	basic: introduce generic ascii_strlower_n() call and make use of it everywhere	Lennart Poettering

2015-11-30	basic: include only what we use	Thomas Hindoe Paaboel Andersen
	This is a cleaned up result of running iwyu but without forward declarations on src/basic.
2015-11-03	util-lib: move character class definitions to string-util.h	Lennart Poettering

2015-11-02	string-util: rework memory_erase() so that it cannot be optimized away	Lennart Poettering
	memory_erase() so far just called memset(), which the compiler might optimize away under certain conditions if it feels there's benefit in it. C11 knows a new memset_s() call that is like memset(), but may not be optimized away. Ideally, we'd just use that call, but glibc currently does not support it. Hence, implement our own simplistic version of it. We use a GCC pragma to turn off optimization for this call, and also use the "volatile" keyword on the pointers to ensure that gcc will use the pointers as-is. According to a variety of internet sources, either one does the trick. However, there are also reports that at least the volatile thing isn't fully correct, hence let's add some snake oil and employ both techniques. https://news.ycombinator.com/item?id=4711346
2015-11-02	Revert "utf8.[ch]: use char32_t and char16_t instead of int, int32_t, int16_t"	Lennart Poettering

2015-10-31	utf8.[ch]: use char32_t and char16_t instead of int, int32_t, int16_t	Shawn Landden
	rework C11 utf8.[ch] to use char32_t instead of uint32_t when referring to unicode chars, to make things more expressive.
2015-10-27	util-lib: split out allocation calls into alloc-util.[ch]	Lennart Poettering

2015-10-27	util: move string_is_safe() to string-util.[ch]	Lennart Poettering

2015-10-24	util-lib: split our string related calls from util.[ch] into its own file ↵	Lennart Poettering
	string-util.[ch] There are more than enough calls doing string manipulations to deserve its own files, hence do something about it. This patch also sorts the #include blocks of all files that needed to be updated, according to the sorting suggestions from CODING_STYLE. Since pretty much every file needs our string manipulation functions this effectively means that most files have sorted #include blocks now. Also touches a few unrelated include files.