From: Adam Jackson <ajax@redhat.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Keith Packard <keithp@keithp.com>,
tfheen@err.no, Daniel Stone <daniels@collabora.com>
Subject: Re: [PATCH] drm: Document code of conduct
Date: Tue, 18 Apr 2017 15:32:01 -0400 [thread overview]
Message-ID: <1492543921.2568.0.camel@redhat.com> (raw)
In-Reply-To: <20170418101057.23737-1-daniel.vetter@ffwll.ch>
On Tue, 2017-04-18 at 12:10 +0200, Daniel Vetter wrote:
> freedesktop.org has adopted a formal&enforced code of conduct:
>
> https://www.fooishbar.org/blog/fdo-contributor-covenant/
> https://www.freedesktop.org/wiki/CodeOfConduct/
>
> Besides formalizing things a bit more I don't think this changes
> anything for us, we've already peer-enforced respectful and
> constructive interactions since a long time. But it's good to document
> things properly.
>
> v2: Drop confusing note from commit message and clarify the grammer
> (Chris, Alex and others).
Acked-by: Adam Jackson <ajax@redhat.com>
- ajax
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-18 19:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 10:10 [PATCH] drm: Document code of conduct Daniel Vetter
2017-04-18 19:32 ` Adam Jackson [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-11 6:48 Daniel Vetter
2017-04-11 7:08 ` Daniel Stone
2017-04-11 7:33 ` Sumit Semwal
2017-04-11 7:51 ` Archit Taneja
2017-04-12 12:59 ` Sumit Semwal
2017-04-11 9:03 ` Daniel Vetter
2017-04-11 9:52 ` Neil Armstrong
2017-04-12 9:35 ` Laurent Pinchart
2017-04-11 9:09 ` Chris Wilson
2017-04-11 9:19 ` Thierry Reding
2017-04-11 9:24 ` Jani Nikula
2017-04-11 9:43 ` Vincent ABRIOU
2017-04-11 10:01 ` Maarten Lankhorst
2017-04-11 10:04 ` Brian Starkey
2017-04-11 12:37 ` Rob Clark
2017-04-11 13:12 ` Luc Verhaegen
2017-04-11 13:24 ` Daniel Vetter
2017-04-11 13:30 ` Luc Verhaegen
2017-04-11 13:36 ` Daniel Vetter
2017-04-11 13:39 ` Luc Verhaegen
2017-04-11 13:58 ` Jani Nikula
2017-04-11 15:14 ` Luc Verhaegen
2017-04-11 15:31 ` Daniel Vetter
2017-04-11 15:48 ` Alex Deucher
2017-04-11 13:35 ` David Herrmann
2017-04-11 13:48 ` Sean Paul
2017-04-11 15:40 ` Harry Wentland
2017-04-11 15:50 ` Alex Deucher
2017-04-11 16:09 ` Daniel Vetter
2017-04-11 17:17 ` Alex Deucher
2017-04-11 16:19 ` Eric Anholt
2017-04-11 17:28 ` Gustavo Padovan
2017-04-12 9:26 ` Michel Dänzer
2017-04-12 13:34 ` Keith Packard
2017-04-14 2:43 ` Gabriel Krisman Bertazi
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=1492543921.2568.0.camel@redhat.com \
--to=ajax@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=tfheen@err.no \
/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