xserver-multidpi/hw
Jamey Sharp 65cedf3905 Kill DoChangeGC in favor of dixChangeGC.
This doesn't change any behavior, but it isn't clear whether NullClient
is correct in all cases. As ajax says,

> For most of these changes, I think it's correct to use NullClient,
> since they are server-initiated changes and should not fail for (eg)
> xace reasons. ... At any rate, you're certainly not changing any
> semantics by leaving them all as NullClient, so this patch can't be
> more wrong than before.

Signed-off-by: Jamey Sharp <jamey@minilop.net>
Reviewed-by: Keith Packard <keithp@keithp.com>
2010-05-12 18:09:55 -07:00
..
dmx SetFontPath: set client->errorValue on failure. 2010-05-12 12:08:38 -07:00
kdrive Replace X-allocation functions with their C89 counterparts 2010-05-13 00:22:37 +07:00
vfb Replace X-allocation functions with their C89 counterparts 2010-05-13 00:22:37 +07:00
xfree86 Kill DoChangeGC in favor of dixChangeGC. 2010-05-12 18:09:55 -07:00
xnest Replace X-allocation functions with their C89 counterparts 2010-05-13 00:22:37 +07:00
xquartz Replace X-allocation functions with their C89 counterparts 2010-05-13 00:22:37 +07:00
xwin Replace X-allocation functions with their C89 counterparts 2010-05-13 00:22:37 +07:00
Makefile.am Catch errors in recursive relink targets 2010-03-22 00:45:57 -05:00