Tanu Kaskinen a604d9cbb3 memblock: multiple references should make blocks read-only ... The old code makes no sense to me. Why would multiple references mean that a previously read-only memblock is suddenly writable? I'm pretty sure that the original intention was to treat multi-referenced blocks as read-only. I don't have any examples where the old code would have caused bad behaviour, however.		2017-04-06 23:36:07 +03:00
..
daemon	sink, source: Add a mode to avoid resampling if possible	2017-01-30 13:54:43 +05:30
modules	pipe-sink: set correct latency	2017-04-06 22:57:23 +03:00
pulse	thread-mainloop: fix volatile use in example	2017-04-06 22:54:46 +03:00
pulsecore	memblock: multiple references should make blocks read-only	2017-04-06 23:36:07 +03:00
tests	thread-test: fix deadlock	2017-01-26 07:56:54 +02:00
utils	build: Use #ifdef to check for #defines	2017-03-08 14:31:29 +01:00
.gitignore	pulse: Add a JSON-parsing library	2016-06-22 21:04:47 +05:30
depmod.py	update FSF addresses to FSF web page	2015-01-14 22:20:40 +02:00
Makefile.am	build-sys: FlatCarbon is dead. Good riddance.	2017-02-27 16:45:49 +02:00
map-file	volume: Add LFE balance API	2015-10-30 09:13:10 +02:00