From: TripleX Chung <triplex@zh-kernel.org>
To: trivial@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Ask for help, about the trivial patches.
Date: Sat, 14 Jul 2007 02:50:40 +0800 [thread overview]
Message-ID: <4697C980.1040902@zh-kernel.org> (raw)
I am working on the chinese translated version of
Documentation/SubmittingPatches and get some problem about the "Trivial
patches".I can not understand what "Trivial patches" exactly means.The
documentation said:
Trivial patches must qualify for one of the following rules:
Spelling fixes in documentation
//Understand
Spelling fixes which could break grep(1)
//Is there any wrong spelling won't break grep(1)?
Warning fixes (cluttering with useless warnings is bad)
//Understand
Compilation fixes (only if they are actually correct)
//Understand
Runtime fixes (only if they actually fix things)
//What kind of runtime fixes? Could anyone give some examples?
Removing use of deprecated functions/macros (eg. check_region)
//Understand
Contact detail and documentation fixes
//Means Contact detail fixes and documentation fixes, right?
Are all the documentation fixes "trivial"?
Non-portable code replaced by portable code (even in arch-specific,
since people copy, as long as it's trivial)
//Do not understand the words in the brackets.
Any fix by the author/maintainer of the file (ie. patch monkey
in re-transmission mode)
//It means if I am the author of a file, when I modify the file, the
patch is trivial, right?
Please give me some advice. Thanks in advance.
next reply other threads:[~2007-07-13 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 18:50 TripleX Chung [this message]
2007-07-13 20:54 ` Ask for help, about the trivial patches Jesper Juhl
2007-07-15 16:30 ` TripleX Chung
2007-07-15 18:44 ` jimmy bahuleyan
2007-07-16 7:51 ` Stefan Richter
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=4697C980.1040902@zh-kernel.org \
--to=triplex@zh-kernel.org \
--cc=linux-kernel@vger.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