From: Chris Wilson <chris@chris-wilson.co.uk>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Thomas Wood <thomas.wood@intel.com>
Subject: Re: [PATCH i-g-t v2] tests: install test programs to libexec
Date: Thu, 26 Mar 2015 16:14:53 +0000 [thread overview]
Message-ID: <20150326161453.GD18055@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1427385927.25724.1.camel@jlahtine-mobl1>
On Thu, Mar 26, 2015 at 06:05:27PM +0200, Joonas Lahtinen wrote:
> Install the test programs by default so that they can be packaged.
>
> v2:
> - Install more tests including scripts and their data
Packaged by whom?
Developers should be using git (otherwise how will they feed back the
patches they generate?), so if you are expecting users to be running them,
please no. Instead write a diagnostic tool.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-26 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 10:43 [PATCH i-g-t] tests: install test programs to libexec Joonas Lahtinen
2015-03-25 12:01 ` Thomas Wood
2015-03-26 16:05 ` [PATCH i-g-t v2] " Joonas Lahtinen
2015-03-26 16:14 ` Chris Wilson [this message]
2015-03-27 6:33 ` Joonas Lahtinen
2015-03-26 17:29 ` Thomas Wood
2015-03-27 7:05 ` Joonas Lahtinen
2015-03-27 8:51 ` [PATCH i-g-t v3] " Joonas Lahtinen
2015-03-27 8:56 ` Joonas Lahtinen
2015-03-31 6:51 ` [PATCH i-g-t v4] " Joonas Lahtinen
2015-03-31 10:04 ` Thomas Wood
2015-03-31 12:53 ` [PATCH i-g-t v5] " Joonas Lahtinen
2015-04-02 16:43 ` Thomas Wood
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=20150326161453.GD18055@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=thomas.wood@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.