From: Theodore Ts'o <tytso@mit.edu>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4:Make the function ext4_ext_tree_init have a return type of void
Date: Mon, 6 Jul 2015 09:06:01 -0400 [thread overview]
Message-ID: <20150706130601.GO8628@thunk.org> (raw)
In-Reply-To: <818AA4A5-2253-45AF-BDD3-C7A7BC501120@gmail.com>
On Mon, Jul 06, 2015 at 08:18:16AM -0400, Nicholas Krause wrote:
> I changed my mind as this seems a good area to start. I will not be
> changing my mind like this for no reason as others feel this is a
> good place to start aftet discussing with mentors on the kernel
> mentors list. Nick
I checked the mailing list archives, and I see nothing to support your
assertion. In fact, quite the contrary. What I found was this
thread:
https://selenic.com/pipermail/kernel-mentors/2015-June/001283.html
At this point, it's not just your lack of technical skills, but the
fact that you constantly seem to have an alternate view of reality
which is why I think Greg K-H has the right of things.
I'm done. I've tried to gently pursaude you to go elsewhere, and
tried to show how both your technical skills and your attitude are
going to be primary blockers for being able to be a contributing
member of the community. It's clear you are unwilling to take my
advice, and at this point, I'd recommend that all other kernel
developers stop trying to work with you.
- Ted
From: Greg KH <greg@kroah.com>
Subject: Unable to convice Greg Kroah Hartman
{sigh} Somehow my filters broke and I started to get your emails again,
they will be fixed after this response.
As I just said, in public, on lkml, in response to one of your recent
patches, I will not accept ANY PATCHES from you AT ALL for the next full
year at the least, maybe longer.
That is my decision, sorry, you will not change my mind, so please go
work on some other project if you really want to help contribute to the
Linux ecosystem. There are loads of other projects out there that need
help. Right now, the kernel community does not need your help at all.
In fact, it has explicitly banned you from it by preventing you from
posting to its mailing lists, an action so huge, I don't know of it ever
happening before.
You are not welcome here.
End of story.
greg k-h
prev parent reply other threads:[~2015-07-06 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1436144944-25343-1-git-send-email-xerofoify@gmail.com>
2015-07-06 2:25 ` [PATCH] ext4:Make the function ext4_ext_tree_init have a return type of void Theodore Ts'o
[not found] ` <818AA4A5-2253-45AF-BDD3-C7A7BC501120@gmail.com>
2015-07-06 13:06 ` Theodore Ts'o [this message]
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=20150706130601.GO8628@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xerofoify@gmail.com \
/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.