All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@fifo99.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Raistlin <raistlin@linux.it>,
	Peter Zijlstra <peterz@infradead.org>,
	claudio@evidence.eu.com, michael@evidence.eu.com, mingo@elte.hu,
	linux-kernel@vger.kernel.org, tglx@linutronix.de,
	johan.eker@ericsson.com, p.faure@akatech.ch,
	Fabio Checconi <fabio@gandalf.sssup.it>,
	Dhaval Giani <dhaval.giani@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Tommaso Cucinotta <tommaso.cucinotta@sssup.it>
Subject: Re: [RFC][PATCH] SCHED_EDF scheduling class
Date: Tue, 22 Sep 2009 17:40:23 -0700	[thread overview]
Message-ID: <1253666423.25689.30.camel@desktop> (raw)
In-Reply-To: <20090922180611.7a47adcc@tpl.lwn.net>

On Tue, 2009-09-22 at 18:06 -0600, Jonathan Corbet wrote:
> On Tue, 22 Sep 2009 16:55:39 -0700
> Daniel Walker <dwalker@fifo99.com> wrote:
> 
> > We did .. It's not my mailer, it's my scripts .. I read a little of
> > wikipedia on this and it says it's a MIME encoding..
> > 
> > http://en.wikipedia.org/wiki/Quoted-printable
> > 
> > So it's like a mime encoded patch instead of plain ascii encoded
> > patch .. I don't think we should all have to parse this stuff out, we
> > should just be getting utf8 encodings which covers everything we use in
> > the kernel AFAIK ..
> 
> I have scripts that handle email as well.  But I wrote them in a
> scripting language which has modules to cope with standard-compliant
> email, and I have no trouble with other transfer encodings at all.  You
> really need to do the same.  Better you fix your scripts than
> continually demanding that the rest of the development community
> conform to your restrictive requirements.

"restrictive requirements" ? I mean don't blame me for that .. It's in
Documentation/email-clients.txt .. The selected norm is UTF8 , and I
don't disagree with that. After researching it that is what we should be
using. At the same time, I'm not demanding anything of anyone , I'm
simply asking nicely for the submitter to check what they are doing..

My scripts may not handle it which is fine. I just wouldn't likely end
up reviewing it. That really isn't bad for _me_ ..

> Daniel, I believe that you are really trying to help make the kernel
> better.  But I fear that you may be having the opposite effect by
> discouraging contributions from others.  Please consider taking a step
> back and thinking about your interactions and the nature of your
> efforts; I think you may find that there are more productive and
> encouraging ways for you to contribute.

I am trying to make the kernel (or community) better, but my motivation
is purely my own (as it often is with people on this list) ..

I don't see the effects your indicating, discouraging contributions .. I
think if anything I'm helping people to get to a place where they can
contribute in a comfortable way without worrying about things like
checkpatch .. I think the problem most submitters have on this list is
that no one tells them they are doing something wrong so they don't
correct it. I clearly recall submitting my first several patches
copy-and-pasted which got either ignored , or caused a maintainer lots
of pain .. Had I been told earlier that it was a problem I would have
corrected it immediately (and been happy to have been notified about
it)..

discouraging contributions is more something that happens when you get
the responses I got earlier in this thread..

Daniel


  reply	other threads:[~2009-09-23  0:40 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 10:30 [RFC][PATCH] SCHED_EDF scheduling class Raistlin
2009-09-22 11:05 ` Peter Zijlstra
2009-09-22 12:51   ` Raistlin
2009-09-22 18:36     ` Peter Zijlstra
2009-09-23 12:19       ` Raistlin
2009-09-23 12:25         ` Dhaval Giani
2009-09-27  6:55       ` Henrik Austad
2009-09-29 16:10         ` Raistlin
2009-09-29 17:34           ` Chris Friesen
2009-09-30 15:58             ` Raistlin
2009-09-30 17:35               ` Chris Friesen
2009-09-22 11:58 ` Claudio Scordino
2009-09-22 12:38   ` Peter Zijlstra
2009-09-24 16:08     ` Claudio Scordino
2009-09-22 13:24 ` Daniel Walker
2009-09-22 14:01   ` Raistlin
2009-09-22 14:02     ` Daniel Walker
2009-09-22 16:42     ` Peter Zijlstra
2009-09-22 19:11       ` Ingo Molnar
2009-09-23  0:51         ` checkpatch as a tool (was Re: [RFC][PATCH] SCHED_EDF scheduling class) Daniel Walker
2009-09-23  1:01           ` Joe Perches
2009-09-23  1:11             ` Daniel Walker
2009-09-23 19:24               ` Andy Isaacson
2009-09-24 14:58                 ` Daniel Walker
2009-09-30 12:06               ` Pavel Machek
2009-09-23 12:22             ` Ingo Molnar
2009-09-23 14:43               ` Daniel Walker
2009-09-30 12:04           ` Pavel Machek
2009-09-23  7:03         ` [RFC][PATCH] SCHED_EDF scheduling class Raistlin
2009-09-23 21:39     ` Steven Rostedt
2009-09-24  0:58       ` GeunSik Lim
2009-09-22 16:38   ` Peter Zijlstra
2009-09-22 23:39   ` Jonathan Corbet
2009-09-22 23:55     ` Daniel Walker
2009-09-23  0:06       ` Jonathan Corbet
2009-09-23  0:40         ` Daniel Walker [this message]
2009-09-23 11:46           ` Avi Kivity
2009-09-23 12:25             ` Ingo Molnar
2009-09-23 14:50               ` Daniel Walker
2009-09-23 14:58                 ` Avi Kivity
2009-09-23 15:08                   ` Daniel Walker
2009-09-23 15:12                     ` Avi Kivity
2009-09-23 15:24                       ` Daniel Walker
2009-09-30 12:05                 ` Pavel Machek
2009-09-22 20:55 ` Linus Walleij
2009-09-23 13:00   ` Raistlin
2009-09-23 13:22   ` Claudio Scordino
2009-09-23 14:08     ` Linus Walleij
2009-09-23 14:45       ` Raistlin
2009-09-23 12:33 ` Linus Walleij
2009-09-23 12:50   ` Linus Walleij
2009-09-23 13:30   ` Raistlin
2009-09-29 18:15     ` roel kluin
2009-09-30 15:59       ` Raistlin
2009-09-24  0:34 ` GeunSik Lim
2009-09-24  6:08   ` Raistlin
2009-09-24  9:11   ` Claudio Scordino

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=1253666423.25689.30.camel@desktop \
    --to=dwalker@fifo99.com \
    --cc=claudio@evidence.eu.com \
    --cc=corbet@lwn.net \
    --cc=dhaval.giani@gmail.com \
    --cc=fabio@gandalf.sssup.it \
    --cc=johan.eker@ericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@evidence.eu.com \
    --cc=mingo@elte.hu \
    --cc=p.faure@akatech.ch \
    --cc=peterz@infradead.org \
    --cc=raistlin@linux.it \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tommaso.cucinotta@sssup.it \
    /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.