gfx-next update: drm-4.8-rc2 tagged in drm-next

[Pete Wright]

On 9/28/16 12:20 AM, Andrei wrote:
> On Wed, 28 Sep 2016 08:49:43 +0300
> Gleb Popov <6yearold at gmail.com> wrote:
>
>> The strangest thing is that he does this trolling from his company's
>> e-mail, which makes me think the guy is actually hacked.
> This is not "company" email. And nobody hacked me.
>
>> If it is really you, I doubt this would make a good advertisement for
>> your services, Andrei. You've been told several times from different
>> people that 1. Patches will go into FreeBSD, not some fork.
> He is never said that patches will go into FreeBSD. All times he is hiding
> from straight answer. He said that this is will be "as port" for "faster
> development". This is bullshit. For this he can use CURRENT.
>

hey guy - mmacy@ specifically said:

"The patches are all awaiting review on phabricator. This work has been 
entirely based on FreeBSD and is done solely for the sake of the 
well-being of the community. "

also - please just stop.  now.  we don't your toxic attitude taking 
resources away from developers doing needed work.

> I found that something really wrong when "drm-next 4.6" was finished and
> no commits in CURRENT. Then 4.7 and nothing! Even now when 4.8 rc2 and
> still you must to download his fork. I will not surprised that "gfx-next"
> patches will never be in FreeBSD.
>
>> 2. You was the first to mention NextBSD at all.
> From: Matthew Macy <mmacy at nextbsd.org>
> http://nextbsd.org/welcome-to-ghost/
> and read subject of email "gfx-NEXT update"
>
> It is so oblivious if you just don't blind.


seriously...relax.  take a deep breath.

*there* *is* *no* *conspiracy* *here*.


can we get back to work please there are still a shit-ton of bugs that 
need to be squashed and we need more devs testing/dogfooding this code 
so it can be gotten into shape so that it can merged back upstream.

-p

-- 
Pete Wright
pete at nomadlogic.org
nomadlogicLA