kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: hugo@carfax.org.uk (Hugo Mills)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Issues with Community
Date: Wed, 17 Sep 2014 11:00:03 +0100	[thread overview]
Message-ID: <20140917100003.GH5783@carfax.org.uk> (raw)
In-Reply-To: <5418C627.5010805@gmail.com>

On Tue, Sep 16, 2014 at 07:22:15PM -0400, nick wrote:
> After numerous tries at good patches and still failing , I am
> listening to what you guys stated about my patches check it applies,
> grammar and build checks. I am still unable to get a good patch and
> would really appreciate it if someone walks me through one good
> patch as I will learn this will a tutor and the tutor can help be my
> router to the community for now in order to start helping me learn
> how to be involved correctly and follow the community rules. I am
> willing to work on my patches if someone is willing to do this for
> me and help me improve my taste in the communities mouth.

   Pretty much everybody who's written you an email from these mailing
lists in the last two months has been trying to help you in this way.
You've consistently ignored (or at least not followed) the advice,
which makes the people who gave it feel like it's not worth the
effort. Therefore, as it stands, anyone considering helping you will
probably think it's a complete waste of time.

   Phrases such as you've used to date: "I must check things more
carefully", "I'm willing to work on my patches", "I will learn this"
are no longer good enough: You've used wording like this before, and
failed to show that you've learned anything as a result.

   So, unless you can explain in detail *why* you ignored all the
previous advice, *and* you can explain in detail *how* you are modifying
your behaviour and working practices so that you can learn from future
advice, nobody is likely to want to help you.

   Go back and read my mail from yesterday. Engage with it -- write
your thoughts and explanations on a point-by-point basis. A single
three-line response at the end of the mail is not sufficient. If you
can't engage with that mail in detail, follow the advice I gave and
seek formal assistance for your learning difficulties.

   Hugo.

-- 
=== Hugo Mills: hugo at ... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
           --- There are three mistaikes in this sentance. ---           
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 811 bytes
Desc: Digital signature
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140917/0dd2fc05/attachment-0001.bin 

  reply	other threads:[~2014-09-17 10:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 23:22 Issues with Community nick
2014-09-17 10:00 ` Hugo Mills [this message]
2014-09-17 10:14   ` Jesus Bustos
2014-09-17 10:18     ` Anuz Pratap Singh Tomar
2014-09-17 10:36 ` Jake Campbell
2014-09-17 13:13 ` Rik van Riel
2014-09-17 17:02   ` Nick Krause
2014-09-17 18:59     ` Sudip Mukherjee
2014-09-17 19:51       ` Jason Conklin
2014-09-17 20:30       ` nick

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=20140917100003.GH5783@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=kernelnewbies@lists.kernelnewbies.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 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).