Yeah, this all seems so unnecessary. I hope Kent can either figure out how to work in the context of a larger team or find somebody who can do it on his behalf.

▲

Voultapher 2 days ago | parent | next [-]

Don't hold your breath.

I've approached Kent two weeks ago and offered to help upstream changes into the kernel so he wouldn't have to interact with any of the kernel people ... he claimed without being able to explain why that having a go-between couldn't possibly help and that if he couldn't dictate the kernel release schedule he wouldn't want to ship the software anyway. And then proceeded to dunk on btrfs.

	▲	yencabulator 16 hours ago \| parent [-]
		Totally expecting to see bcacheos next. (Then maybe down the line people will realize Linus had a heart of gold behind his foul mouth.)

▲

johnisgood 2 days ago | parent | prev [-]

> Once the BCacheFS maintainer behaves [...]

So, there are still behavioral issues here I take it? That is a bummer. This is not news to me, but I thought the situation has changed ever since.

▲

motorest 2 days ago | parent [-]

> So, there are still behavioral issues here I take it?

From the past discussion, it's mainly grave behavioral issues but they also end up being technical. Such as trying to push new untested features into RCs and breaking builds, and resorting to flame wars to push these problematic patches forward instead of actually working them out with maintainers.

But yeah, the final straw was a very abusive email sent to a maintainer in the mailing list.

	▲	koverstreet a day ago \| parent [-]
		...Where are you getting this stuff? Seriously, every time I read tales about all the horrific things I've done in the kernel community, the stories grow and get wilder and wilder. Oh wait. It's you.