From: Petri Latvala <petri.latvala@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: IGT development <igt-dev@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 2/2] autoconf: Drop gtkdoc support
Date: Thu, 13 Dec 2018 15:08:30 +0200 [thread overview]
Message-ID: <20181213130830.GQ17124@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20181213124355.1420-2-daniel.vetter@ffwll.ch>
On Thu, Dec 13, 2018 at 01:43:55PM +0100, Daniel Vetter wrote:
> It's a huge kludge (doesn't track dependencies correctly) and compared
> to the meson one, real slow. Throw it out.
>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Documentation building works with meson? Check
Automatic documentation builds available, by meson, from gitlab? Check
Seems like we're good to go with this, unless CI reports some weird
and hilarious build failure after removal, so
Acked-by: Petri Latvala <petri.latvala@intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-12-13 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 12:43 [igt-dev] [PATCH i-g-t 1/2] README: Use meson for building docs Daniel Vetter
2018-12-13 12:43 ` [igt-dev] [PATCH i-g-t 2/2] autoconf: Drop gtkdoc support Daniel Vetter
2018-12-13 13:08 ` Petri Latvala [this message]
2018-12-13 15:46 ` Daniel Vetter
2018-12-13 13:05 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] README: Use meson for building docs Patchwork
2018-12-13 13:06 ` [igt-dev] [PATCH i-g-t 1/2] " Petri Latvala
2018-12-13 16:02 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/2] " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181213130830.GQ17124@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox