From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Eric Engestrom <eric.engestrom@imgtec.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH maintainer-tools 1/3] make: run check on current `dim`, not the installed one
Date: Wed, 05 Apr 2017 14:29:57 +0300 [thread overview]
Message-ID: <87shlnytvu.fsf@intel.com> (raw)
In-Reply-To: <20170405111525.32602-1-eric.engestrom@imgtec.com>
On Wed, 05 Apr 2017, Eric Engestrom <eric.engestrom@imgtec.com> wrote:
> Signed-off-by: Eric Engestrom <eric.engestrom@imgtec.com>
For me "current dim" *is* the "installed one". ;)
Pushed patches 1-2.
BR,
Jani.
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index b4cea98..4291049 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -33,7 +33,7 @@ shellcheck:
> shellcheck $(SC_EXCLUDE) dim bash_completion
>
> mancheck:
> - @for cmd in $$(dim list-commands); do \
> + @for cmd in $$(./dim list-commands); do \
> if ! grep -q "^$$cmd" dim.rst; then \
> echo "$@: $$cmd not documented"; \
> fi \
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-04-05 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 11:15 [PATCH maintainer-tools 1/3] make: run check on current `dim`, not the installed one Eric Engestrom
2017-04-05 11:15 ` [PATCH maintainer-tools 2/3] dim: send 'not configured' error to stderr Eric Engestrom
2017-04-05 11:15 ` [PATCH maintainer-tools 3/3] dim.rst: update CONTRIBUTING instructions Eric Engestrom
2017-04-05 11:25 ` Jani Nikula
2017-04-05 12:12 ` Daniel Vetter
2017-04-05 11:29 ` Jani Nikula [this message]
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=87shlnytvu.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.engestrom@imgtec.com \
--cc=intel-gfx@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 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.