From: Dave Martin <dave.martin@linaro.org>
To: "Theodore Ts'o" <tytso@mit.edu>,
Tekkaman Ninja <tekkamanninja@gmail.com>,
Harry Wei <harryxiyou@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH]Documentation: Chinese translation of Documentation/arm/kernel_user_helpers.txt
Date: Wed, 31 Oct 2012 12:06:19 +0100 [thread overview]
Message-ID: <20121031110619.GC3780@linaro.org> (raw)
In-Reply-To: <20121030190349.GC5044@thunk.org>
On Tue, Oct 30, 2012 at 03:03:49PM -0400, Theodore Ts'o wrote:
> On Wed, Oct 31, 2012 at 12:20:04AM +0800, Tekkaman Ninja wrote:
> > This is a Chinese translated version of
> > Documentation/arm/kernel_user_helpers.txt
> >
> > Signed-off-by: Fu Wei <tekkamanninja@gmail.com>
>
> I wonder if it woiuld be a good idea to note the git commit id of the
> kernel version that was used as the source document for the
> translation. That way in the future, someone can just do a "git log
> -p" to find all of the changes since the original version of the
> translation, and use that to update the translation.
>
> Just a suggestion,
What's the best way of making sure that changes in the source document
propagate to translated versions?
It might be enough to put a note in the source document to remind people
to check for the extistence of translated versions and CC the relevant
translation maintianers with any patches affecting the source document.
Cheers
---Dave
next prev parent reply other threads:[~2012-10-31 11:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 16:20 [PATCH]Documentation: Chinese translation of Documentation/arm/kernel_user_helpers.txt Tekkaman Ninja
2012-10-30 19:03 ` Theodore Ts'o
2012-10-31 10:44 ` harryxiyou
2012-10-31 11:06 ` Dave Martin [this message]
2012-10-31 21:34 ` Theodore Ts'o
2012-11-01 14:23 ` Dave Martin
2012-10-31 5:06 ` Dongsheng Song
2012-10-31 10:42 ` harryxiyou
2012-10-31 13:59 ` Ninja Tekkaman
2012-10-31 13:56 ` Ninja Tekkaman
2012-10-31 11:03 ` Dave Martin
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=20121031110619.GC3780@linaro.org \
--to=dave.martin@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=harryxiyou@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=tekkamanninja@gmail.com \
--cc=tytso@mit.edu \
/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.