From: Jani Nikula <jani.nikula@linux.intel.com>
To: Sean Paul <seanpaul@chromium.org>, Daniel Vetter <daniel@ffwll.ch>
Cc: DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: RFC: late drm pull requests and other topics
Date: Tue, 07 Mar 2017 18:51:43 +0200 [thread overview]
Message-ID: <87k281f2sg.fsf@intel.com> (raw)
In-Reply-To: <20170307145404.GA10298@art_vandelay>
On Tue, 07 Mar 2017, Sean Paul <seanpaul@chromium.org> wrote:
> On Tue, Mar 07, 2017 at 01:11:43AM +0100, Daniel Vetter wrote:
>> Linus shitting on dri-devel
>> ---------------------------
>>
> IMO, the best approach is to do exactly what danvet did last time:
> praise the contributor for their work and reiterate the list rule that
> one must be respectful on dri-devel.
Agreed, I prefer this over Bcc.
>> Splitting the drm pull
>> ----------------------
>>
> Yeah, I feel like if we split things up, Linus would likely be even more
> unhappy. Even with very careful planning, the drm core changes so frequently
> that things are bound to drift. drm-misc does a good job of mostly solving that
> issue, and having Dave between the subtree chaos and Linus is very valuable.
Agreed.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-07 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 0:11 RFC: late drm pull requests and other topics Daniel Vetter
2017-03-07 14:54 ` Sean Paul
2017-03-07 16:51 ` Jani Nikula [this message]
2017-03-07 15:56 ` Alex Deucher
2017-03-07 19:51 ` Lukas Wunner
2017-03-07 20:45 ` Alex Deucher
2017-03-07 16:42 ` Jani Nikula
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=87k281f2sg.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=seanpaul@chromium.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.