On 11/13/18 08:50 PM, Keith Packard wrote:
Alan Coopersmith writes:
3rd choice - this seems to work for me, shipping a file named README in the
tarball without any Makefile modifications:
Yikes! Scary git-fu!
Maybe we can see if cmark-gfm is available? That's the github fork that
parses
On Tue, Nov 13, 2018 at 08:50:11PM -0800, Keith Packard wrote:
> Alan Coopersmith writes:
>
> > 3rd choice - this seems to work for me, shipping a file named README in the
> > tarball without any Makefile modifications:
>
> Yikes! Scary git-fu!
>
> Maybe we can see if cmark-gfm is available?
Alan Coopersmith writes:
> 3rd choice - this seems to work for me, shipping a file named README in the
> tarball without any Makefile modifications:
Yikes! Scary git-fu!
Maybe we can see if cmark-gfm is available? That's the github fork that
parses more useful common mark syntax files, which
hi,
On Tue, Nov 13, 2018, 7:57 PM Alan Coopersmith Anyone have a preference? Shipping README.md seems easier - will it cause
> problems for any distros or packagers?
>
i think README.md is the right way to go. presumably any packaging
challenges have been ironed out by now considering how
On 11/13/18 04:57 PM, Alan Coopersmith wrote:
On 11/13/18 05:41 AM, Julien Cristau wrote:
LGTM. Thanks Alan!
Thanks to you, Peter, & Ray for reviews. I merged this, and thought
"Okay, time to cut a new release." And then I found the mistake.
automake automatically includes a file named
On 11/13/18 05:41 AM, Julien Cristau wrote:
LGTM. Thanks Alan!
Thanks to you, Peter, & Ray for reviews. I merged this, and thought
"Okay, time to cut a new release." And then I found the mistake.
automake automatically includes a file named "README" in the tarball.
It does not include a
The QXL driver names its outputs starting at 0 (e.g. Virtual-0,
Virtual-1, etc). This code was presumably copy/pasted from a different
driver, and is not necessary for the QXL driver. Other drivers simply
use the kernel connector_type_id which starts at 1. For example, the
modesetting driver
On Mon, 2018-11-12 at 13:48 -0800, Manoj Gupta wrote:
> Is this the right mailing list for this patch? If not, please advise.
This is the right list, although we're generally moving to gitlab for
patch submission:
https://gitlab.freedesktop.org/xorg/xserver/
> diff --git a/config/udev.c
On Mon, 2018-11-12 at 13:51 +0100, Michal Srb wrote:
> The screensaver can regularly move its window to random offsets. It should
> use the ConfigureWindow function instead of calling the Screen's MoveWindow
> directly. Some MoveWindow implementations, such as compMoveWindow, rely on
> Screen's
Title should be "Make output name numbering 1-based"
>
> The QXL driver names its outputs starting at 0 (e.g. Virtual-0,
> Virtual-1, etc). This code was presumably copy/pasted from a different
> driver, and is not necessary for the QXL driver. Other drivers simply
> use the kernel
Hi All,
I recently ran into compiler errors when building xwayland in Chrome
OS related to use of major()/minor() in config/udev.c.
The patch fixing the problem by including "xorg-config.h" and
.
Is this the right mailing list for this patch? If not, please advise.
Thanks,
Manoj
[PATCH]
11 matches
Mail list logo