From: Keiichi KII <k-keiichi@bx.jp.nec.com>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de, apw@shadowen.org
Subject: Re: [PATCH 2/2] add SubmittingPatches to Documentation/ja_JP
Date: Fri, 26 Oct 2007 20:48:11 +0900 [thread overview]
Message-ID: <4721D3FB.6040401@bx.jp.nec.com> (raw)
In-Reply-To: <20071026.161252.118133301.yoshfuji@linux-ipv6.org>
Thank you for your reply!
> Basically okay, but please refer to the original DCO
> document.
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.
If not so, please tell me about 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).
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.
Thanks
> --yoshfuji
>
> In article <47218F5C.1040402@bx.jp.nec.com> (at Fri, 26 Oct 2007 15:55:24 +0900), Keiichi KII <k-keiichi@bx.jp.nec.com> says:
>
>> 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
>>
>>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
--
Keiichi KII
NEC Corporation OSS Platform Development Division
E-mail: k-keiichi@bx.jp.nec.com
prev parent reply other threads:[~2007-10-26 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 6:48 [PATCH 0/2] Japanese translation of Documentation/SubmittingPatches Keiichi KII
2007-10-26 6:51 ` [PATCH 1/2] fix typo in SubmittingPatches Keiichi KII
2007-10-27 3:50 ` Randy Dunlap
2007-10-29 10:50 ` Keiichi KII
2007-10-29 10:51 ` Keiichi KII
2007-10-26 6:55 ` [PATCH 2/2] add SubmittingPatches to Documentation/ja_JP Keiichi KII
2007-10-26 7:12 ` YOSHIFUJI Hideaki / 吉藤英明
2007-10-26 11:48 ` Keiichi KII [this message]
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=4721D3FB.6040401@bx.jp.nec.com \
--to=k-keiichi@bx.jp.nec.com \
--cc=apw@shadowen.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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