From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: jimmy bahuleyan <knight.camelot@gmail.com>
Cc: TripleX Chung <triplex@zh-kernel.org>,
Jesper Juhl <jesper.juhl@gmail.com>,
trivial@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Ask for help, about the trivial patches.
Date: Mon, 16 Jul 2007 09:51:14 +0200 [thread overview]
Message-ID: <469B2372.2040004@s5r6.in-berlin.de> (raw)
In-Reply-To: <469A6B1A.2040908@gmail.com>
jimmy bahuleyan wrote:
> TripleX Chung wrote:
>> But I still have problems.
>> Trivial means "of little worth or importance". But some of the examples
>> in the rules are important, like "runtime fixes". Spell fixes must be
>> unimportant, but most of the runtime fixes like memory leaks or NULL
>> pointers must be important. I was still a little confused with them.
>>
>
> Literally, yes. But look at it from a s/w engineering point of view.
>
> A NULL pointer deref is important, but it is also a *very local* and
> very obvious fix (one that doesn't need extensive testing, one that
> doesn't have effects spread out over many modules that requires great
> amount of thought).
>
> So such things are trivial bug-fixes.
Yes; it's more the /handling/ of the patch that is "trivial" in a strict
sense. Bug fixes should usually go through maintainers. But for fixes
which are obvious == easy to verify, trivial@kernel.org makes sense as a
central point for submitters to turn to, to lower the barrier for
submission.
--
Stefan Richter
-=====-=-=== -=== =----
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-07-16 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 18:50 TripleX Chung
2007-07-13 20:54 ` Jesper Juhl
2007-07-15 16:30 ` TripleX Chung
2007-07-15 18:44 ` jimmy bahuleyan
2007-07-16 7:51 ` Stefan Richter [this message]
2007-07-15 21:29 ` Jesper Juhl
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=469B2372.2040004@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=jesper.juhl@gmail.com \
--cc=knight.camelot@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=triplex@zh-kernel.org \
--cc=trivial@kernel.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
all inboxes | Powered by JetHome®