From: Jani Nikula <jani.nikula@linux.intel.com>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 3/3] dim: Backronym
Date: Tue, 28 Mar 2017 12:27:20 +0300 [thread overview]
Message-ID: <87a8857nuv.fsf@intel.com> (raw)
In-Reply-To: <20170327084546.4711-3-daniel.vetter@ffwll.ch>
On Mon, 27 Mar 2017, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> It's kinda beyond just drm-intel nowadays ...
>
> Idea from Jani on irc.
Hah, it was a bit tongue-in-cheek, but works for me!
Ack also on patch 1.
BR,
Jani.
>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
> dim.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/dim.rst b/dim.rst
> index be541d80ec7e..87a8906aad8d 100644
> --- a/dim.rst
> +++ b/dim.rst
> @@ -2,9 +2,9 @@
> dim
> =====
>
> ----------------------------
> -drm-intel maintainer script
> ----------------------------
> +--------------------------------
> +drm inglorious maintainer script
> +--------------------------------
>
> :Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> :Author: Jani Nikula <jani.nikula@intel.com>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-28 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 8:45 [PATCH 1/3] drm: Document maintainer duties Daniel Vetter
2017-03-27 8:45 ` [PATCH 2/3] dim: Review subcommand docs Daniel Vetter
2017-03-27 8:49 ` Daniel Vetter
2017-03-28 9:24 ` Jani Nikula
2017-03-27 8:45 ` [PATCH 3/3] dim: Backronym Daniel Vetter
2017-03-28 9:27 ` Jani Nikula [this message]
2017-04-03 10:59 ` [PATCH 1/3] drm: Document maintainer duties Eric Engestrom
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=87a8857nuv.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox