Re: Cannot submit merge request for xf86-video-intel

2019-05-13 Thread Adam Richter
On Mon, May 13, 2019, 4:00 PM Adam Jackson wrote: > On Sat, 2019-05-11 at 21:17 +0200, Maarten Maathuis wrote: > > Given that the xf86-video-intel repo hasn't been been set up for PRs > > it seems (as opposed to lets say the xserver). > > I see in https://gitlab.freedesktop.org/xorg/driver/xf86-v

Fwd: Cannot submit merge request for xf86-video-intel

2019-05-11 Thread Adam Richter
Linux, but I imagine might still be used in some circumstances. Anyhow, my original email to intel-gfx, appended here, covers this in slightly more detail. Any advice on how I should proceed is welcome. Thanks in advance for any thoughts on this. Adam -- Forwarded message ----- Fro

Re: Proposed addition to CodingStyle web page about assert(a && b)

2019-05-07 Thread Adam Richter
On Sun, May 5, 2019 at 7:18 AM walter harms wrote: > Am 05.05.2019 09:11, schrieb Matthieu Herrb: > > On Sat, May 04, 2019 at 03:47:31PM -0700, Adam Richter wrote: > >> Hi, everyone. > >> > >> I would like to propose that whoever has the ability to edit t

Proposed addition to CodingStyle web page about assert(a && b)

2019-05-04 Thread Adam Richter
Hi, everyone. I would like to propose that whoever has the ability to edit the web page add a line like the following to https://www.x.org/wiki/CodingStyle/ : - Separate assert(a && b) into assert(a) and assert(b). I can think of several potential advantages of separating logical conjunctions i

Re: Would any Apple user be kind enough to check this trivial X server patch?

2019-05-04 Thread Adam Richter
ks in advance for any further review of this. Adam On Thu, May 2, 2019 at 1:02 PM Adam Richter wrote: > > Hi. > > The attached patch fixes three places in hw/xquartz/darwin.c that > relied on side effects in assert parameters. That is, they would fail > if assert() were replace

Would any Apple user be kind enough to check this trivial X server patch?

2019-05-02 Thread Adam Richter
Hi. The attached patch fixes three places in hw/xquartz/darwin.c that relied on side effects in assert parameters. That is, they would fail if assert() were replaced with a macro that did not evaluate its parameters. I would appreciate it if anyone with an appropriate Apple system would try this