Enrico Weigelt, metux IT consult 3a6bcb854e (!1682) os: log: drop now meaningless XLOG_FLUSH option ... Since we're not indirectly writing via FILE anymore, this option has become meaningless: it meant flushing out our in-process buffer to the kernel, but we're now doing direct write() calls anyways. xf86 still accepts the "flush" config file flag for backwards compatibility, but it hasn't any practical meaning anymore. Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>		2024-10-31 19:23:51 +01:00
..
kdrive	(!1714) kdrive: xv: use window destructor hook	2024-10-31 19:23:51 +01:00
vfb	(!1711) vfb: use dixDestroyPixmap() instead of direct driver call	2024-10-31 19:23:50 +01:00
xfree86	(!1682) os: log: drop now meaningless XLOG_FLUSH option	2024-10-31 19:23:51 +01:00
xnest	(!1711) xnest: use dixDestroyPixmap() instead of direct driver call	2024-10-31 19:23:50 +01:00
xquartz	xquartz: drop unused code	2024-10-10 16:42:38 +00:00
xwayland	(!1714) xwayland: use window destructor hook	2024-10-31 19:23:51 +01:00
xwin	(!1682) os: log: drop now meaningless XLOG_FLUSH option	2024-10-31 19:23:51 +01:00
meson.build	Drop DMX DDX	2021-09-07 09:34:31 +00:00