All of lore.kernel.org
 help / color / mirror / Atom feed
From: chambilkethakur@gmail.com (Anuz Pratap Singh Tomar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Bad Patches and Issues with other devolopers
Date: Tue, 5 Aug 2014 19:28:15 +0100	[thread overview]
Message-ID: <CAJnfX5vpgW6a_zoRepkNH8jNADxwU+PLkO9x4f21MQX9XjjH_A@mail.gmail.com> (raw)
In-Reply-To: <CAPDOMViYfAh8UUCaYbgNBCH5J9vL2V+vpciYFc=RCL4FnbLxew@mail.gmail.com>

On Tue, Aug 5, 2014 at 7:04 PM, Nick Krause <xerofoify@gmail.com> wrote:

> On Tue, Aug 5, 2014 at 1:59 PM, Mandeep Sandhu
> <mandeepsandhu.chd@gmail.com> wrote:
> > Hi Nick,
> >
> > I came across some G+ posts from kernel developers discussing you and
> > your recent patch submissions. I must say you're pretty (in)famous! :)
> >
> > Jokes aside, why not just follow on the advice given to you by so many
> > people, i.e pick an area of interest (in the various kernel
> > subsystems) for yourself, first pick really small ossues (but not the
> > code formatting ones as they only tend to generate noise for the
> > maintainer and not really fix anything), create the patch, see if the
> > kernel builds with. TEST IT, most importantly (if you don't have the
> > requisite hw then either acquire one, or pick another issue where you
> > CAN test it). Basically check everything thats mentioned here:
> >
> > https://www.kernel.org/doc/Documentation/SubmittingPatches
> > http://kernelnewbies.org/OPWfirstpatch
> >
> > Trust me, if you _do_ go through this process and submit a 'good'
> > patch, all past issues that you've had with other developers will be
> > forgotten.
> >
> > Don't be in a rush to get 'something' in the kernel. I know its a big
> > deal to get things in one of the coolest piece of software on this
> > planet, but you'll need a lot perseverance and patience to be a kernel
> > contributor.
> >
> > HTH,
> > -mandeep
> >
> >
> > On Tue, Aug 5, 2014 at 10:42 AM, Nick Krause <xerofoify@gmail.com>
> wrote:
> >> I have sent out just ten bad patches and the developers seem very
> >> annoyed with me and
> >> think I am trolling. If someone on this list can find a way for me to
> >> improve my relationship
> >> with them and let me continue my work here that would be great.
> >> Nick
> >>
> >> _______________________________________________
> >> Kernelnewbies mailing list
> >> Kernelnewbies at kernelnewbies.org
> >> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
> That's fine,
> I feel perhaps I am just really trying to force my code in(ego) and
> just is bad form.
> If anyone on this list can read my last trace to check my logic first,
> before I write
> a patch and let you check it, that would be great.
> Thanks A lot,
> Nick
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

How about not sending patches at all until you develop a good understanding
of kernel subsystems.
read the books and read code for few months before you ever re-try sending
patches?

-- 
Thank you
Warm Regards
Anuz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140805/b3ddab04/attachment.html 

  reply	other threads:[~2014-08-05 18:28 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 17:42 Bad Patches and Issues with other devolopers Nick Krause
2014-08-05 17:56 ` Kristofer Hallin
2014-08-05 17:59 ` Mandeep Sandhu
2014-08-05 18:04   ` Nick Krause
2014-08-05 18:28     ` Anuz Pratap Singh Tomar [this message]
2014-08-05 18:25 ` Sudip Mukherjee
2014-08-05 19:52   ` Rohan Puri
2014-08-05 19:54 ` Valdis.Kletnieks at vt.edu
2014-08-05 20:20   ` Nick Krause
     [not found]     ` <alpine.LFD.2.11.1408051702460.26301@localhost>
2014-08-05 21:35       ` Nick Krause
2014-08-05 22:49         ` Greg Freemyer
2014-08-05 23:43           ` Nick Krause
2014-08-06  9:48             ` Anuz Pratap Singh Tomar
2014-08-06 10:02               ` Pramod Gurav
2014-08-06 10:30                 ` Anuz Pratap Singh Tomar
2014-08-06 12:47                   ` Nick Krause
2014-08-06 13:25                     ` Nick Krause
2014-08-06 13:28                       ` Kristofer Hallin
2014-08-06 13:32                         ` Nick Krause
2014-08-06 13:45                           ` Sudip Mukherjee
2014-08-06 13:46                           ` Anuz Pratap Singh Tomar
2014-08-06 13:56                             ` Nick Krause
2014-08-06 13:59                               ` Andev
2014-08-06 14:07                                 ` Nick Krause
2014-08-06 14:22                                   ` Nick Krause
2014-08-06 14:30                                     ` Kristofer Hallin
2014-08-06 13:35                       ` Robert P. J. Day
2014-08-06 16:31                         ` Josh Carlson
2014-08-06 16:47                           ` Nick Krause
2014-08-06 17:11                             ` Greg Freemyer
2014-08-06 17:16                               ` Nick Krause
2014-08-06 16:52                           ` Mandeep Sandhu
2014-08-06 16:58                             ` Nick Krause
2014-08-06 16:58               ` Valdis.Kletnieks at vt.edu
2014-08-06 17:03                 ` Nick Krause
2014-08-06 17:24                 ` Robert P. J. Day
2014-08-06 18:05                   ` Nick Krause
2014-08-06 18:08                     ` Nick Krause
2014-08-06 18:30                     ` Lidza Louina
2014-08-06 18:33                       ` Nick Krause
2014-08-06 18:42                         ` Lidza Louina
2014-08-06 18:45                           ` Nick Krause
2014-08-06 18:53                             ` Kristofer Hallin
2014-08-06 18:56                               ` Nick Krause
2014-08-06 20:45                               ` StephanT

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=CAJnfX5vpgW6a_zoRepkNH8jNADxwU+PLkO9x4f21MQX9XjjH_A@mail.gmail.com \
    --to=chambilkethakur@gmail.com \
    --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 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.