linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Nick Krause <xerofoify@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Work on ext4
Date: Fri, 25 Jul 2014 10:59:46 -0400	[thread overview]
Message-ID: <20140725145946.GT1865@thunk.org> (raw)
In-Reply-To: <CAPDOMVi_qXwY3R2fYiSwu9Bs2fA4kwamt3TKzVEZOZmuaLkbMA@mail.gmail.com>

On Thu, Jul 24, 2014 at 10:29:49PM -0400, Nick Krause wrote:
> Sorry about my other issues Ted. But if you would like to give
> me a change, I would like to help out on ext4 development.
> Just tell me what I should read before I start helping out:).

So here's my concern.  The patches and questions which you've sent to
LKML seem to indicate either that (a) you are incredibly sloppy, (b)
you're technically not very capable, or (c) you were so enthusiastic
to Make A Difference that you were sending out patches and asking
questions without spending any time to think, test, and spending time
doing research.

Whichever it is, the worry to me is that you will consume far more of
my time and other developers than the actual effort you will actually
end up contributing.  So the "help" ends up sucking away precious
developer time and bandwidth.

If you can send pointers to actual technical work you've done that
might pursuade folks that you can actually contribute in a positive
fashion, that might be helpful.

Regards,

						- Ted

  reply	other threads:[~2014-07-25 14:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25  2:29 Work on ext4 Nick Krause
2014-07-25 14:59 ` Theodore Ts'o [this message]
2014-07-25 15:22   ` Nick Krause
2014-07-25 15:41     ` Theodore Ts'o
2014-07-25 16:07       ` Eric Sandeen
2014-07-28  4:01         ` Nick Krause
2014-07-28 12:45           ` Theodore Ts'o
2014-07-28 15:17             ` Nick Krause
2014-07-25 15:24 ` Wang Shilong
2014-07-25 15:59   ` Nick Krause
2014-07-25 16:06     ` Nick Krause

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=20140725145946.GT1865@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).