jspran...@awlship.com wrote:
Trying to build Kdrive and I receiving the following errors:
kinput.c: In function ‘KdEnableInput’:
kinput.c:340: warning: passing argument 1 of ‘NoticeEventTime’ from
incompatible pointer type
kinput.c: In function ‘KdQueueEvent’:
kinput.c:1675: warning:
On Tue, Jun 09, 2009 at 03:04:19PM +, jspran...@awlship.com wrote:
Trying to build Kdrive and I receiving the following errors:
kinput.c: In function ‘KdEnableInput’:
kinput.c:340: warning: passing argument 1 of ‘NoticeEventTime’ from
incompatible pointer type
kinput.c: In function
On Mon, Jun 08, 2009 at 04:20:00PM -0400, Adam Jackson wrote:
Security is handled out of band like any other project. We'll release
patches for at least the most recent release, probably do a point
release for same, and anyone shipping anything older gets to backport.
In practise, this didn't
Joerg Sonnenberger wrote:
On Mon, Jun 08, 2009 at 04:20:00PM -0400, Adam Jackson wrote:
Security is handled out of band like any other project. We'll release
patches for at least the most recent release, probably do a point
release for same, and anyone shipping anything older gets to
Joerg Sonnenberger wrote:
On Tue, Jun 09, 2009 at 07:05:47AM -0700, Alan Coopersmith wrote:
Joerg Sonnenberger wrote:
On Mon, Jun 08, 2009 at 04:20:00PM -0400, Adam Jackson wrote:
Security is handled out of band like any other project. We'll release
patches for at least the most recent
On Tue, Jun 09, 2009 at 08:13:03AM -0700, Alan Coopersmith wrote:
Assuming you mean
http://cgit.freedesktop.org/xorg/lib/libXfont/commit/?id=5bf703700ee4a5d6eae20da07cb7a29369667aef
the patch is available from git, like all other changes.
See earlier part about following git history :)
I
Where are the release engineering schedule, policies, and steps
documented?
Note: I have done at least three official X.org component releases (at
least three different modules). (Official is defined as: I increased
number for release version, did tests, tagged in git, created tarballs,
maybe
On Mon, 2009-06-08 at 12:24 -0500, Jeremy C. Reed wrote:
- what has the elected board discussed for improving or changing the
release engineering processes and scheduling?
Just to address this one point, recall that the Board is explicitly not
a technical body. It exists to govern the
On Mon, Jun 8, 2009 at 1:20 PM, Adam Jacksona...@nwnk.net wrote:
Testing is... informal is the polite word. Nobody's stepped up to do it
rigorously, so no one does it.
Peter poked me a while ago to work on autotooling xtest. I have it
just about working nicely to where you just run make check
