From: Keiichi Kii <k-keiichi@bx.jp.nec.com>
Hi all,
Currently, HOWTO and stable_api_nonsense.txt are included in
Documentation/"each country"/ as policy documents.
Greg K-H said the following in this thread:SubmittingPatches document includes important information
about how to generate patch and write e-mail related to kernel
development.So, I wish SubmittingPatches is included in Documentation/"each country"/
as policy documents.
How do you think about this?I attach two patches(one fixes a typo, the other adds SubmittingPatches
translated into Japanese to Documentation/ja_JP directory).
These patches are for linux-2.6.23.The translated SubmittingPatches has already been reviewed by JF project.
JF project is the Japanese equivalent of LDP.Your comments are very welcome.
Signed-off-by: Keiichi Kii <k-keiichi@bx.jp.nec.com>
--
Keiichi KII
NEC Corporation OSS Platform Development Division
E-mail: k-keiichi@bx.jp.nec.com-
From: Keiichi Kii <k-keiichi@bx.jp.nec.com>
This patch adds SubmittingPatches translated into Japanese to
Documentation/ja_JP directory.I attach the patch because there is a possibility that MUA
will change the character encoding sometimes.Signed-off-by: Keiichi KII <k-keiichi@bx.jp.nec.com>
--
Keiichi KII
NEC Corporation OSS Platform Development Division
E-mail: k-keiichi@bx.jp.nec.com
Hello.
Basically okay, but please refer to the original DCO
document.Your mailer is broken. You should include "charset" parameter
in your multipart. Maybe it is better to prepare a git repository,
or attach it as a binary (application/octet-stream).--yoshfuji
-
What is "DCO document"?
DCO stands for Developer's Certificate of Origin in SumittingPatches?
If so, I will put original text of the DCO into the translated SubmittingPatches.Thanks, I couldn't notice possibility of false recognition of character code
because there was no probelm in my environment.
But, I used mew as MUA and the patch was recognized as Ascii, not UTF-8.
I think alternative based on your suggestions.--
Keiichi KII
NEC Corporation OSS Platform Development Division
E-mail: k-keiichi@bx.jp.nec.com-
From: Keiichi Kii <k-keiichi@bx.jp.nec.com>
Fix typo.
Signed-off-by: Keiichi Kii <k-keiichi@bx.jp.nec.com>
Cc: Andy Whitcroft <apw@shadowen.org>
---
Index: trunk/Documentation/SubmittingPatches
===================================================================
--- trunk.orig/Documentation/SubmittingPatches
+++ trunk/Documentation/SubmittingPatches
@@ -464,7 +464,7 @@ section Linus Computer Science 101.
Nuff said. If your code deviates too much from this, it is likely
to be rejected without further review, and without comment.-Once significant exception is when moving code from one file to
+One significant exception is when moving code from one file to
another in this case you should not modify the moved code at all in
the same patch which moves it. This clearly delineates the act of
moving the code and your changes. This greatly aids review of the--
Keiichi KII
NEC Corporation OSS Platform Development Division
E-mail: k-keiichi@bx.jp.nec.com
-
From: Keiichi Kii <k-keiichi@bx.jp.nec.com>
Greg, could you replace old patch with new one?
Fix typo and insert " -- " between clauses.
Signed-off-by: Keiichi Kii <k-keiichi@bx.jp.nec.com>
Cc: Andy Whitcroft <apw@shadowen.org>
---
Index: trunk/Documentation/SubmittingPatches
===================================================================
--- trunk.orig/Documentation/SubmittingPatches
+++ trunk/Documentation/SubmittingPatches
@@ -464,8 +464,8 @@ section Linus Computer Science 101.
Nuff said. If your code deviates too much from this, it is likely
to be rejected without further review, and without comment.-Once significant exception is when moving code from one file to
-another in this case you should not modify the moved code at all in
+One significant exception is when moving code from one file to
+another -- in this case you should not modify the moved code at all in
the same patch which moves it. This clearly delineates the act of
moving the code and your changes. This greatly aids review of the
actual differences and allows tools to better track the history of--
Keiichi KII
NEC Corporation OSS Platform Development Division
E-mail: k-keiichi@bx.jp.nec.com
-
That first sentence is still broken. It should be more like this,
with either a ":" or ";" or " -- " between clauses:One significant exception is when moving code from one file to
another -- in this case you should not modify the moved code at all in
the same patch which moves it.---
~Randy
-
Tahnks for your point.
I will fix this sentence as above.--
Keiichi KII
NEC Corporation OSS Platform Development Division
E-mail: k-keiichi@bx.jp.nec.com
-
| Faik Uygur | Re: Linux 2.6.21-rc1 |
| pageexec | Re: [stable] Linux 2.6.25.10 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Mark Lord | Re: 2.6.25-rc8: FTP transfer errors |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
