mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Thu, 1 Nov 2012 15:23:38 +0100	[thread overview]
Message-ID: <20121101142338.GA29971@linaro.org> (raw)
In-Reply-To: <20121031213415.GB17305@thunk.org>

On Wed, Oct 31, 2012 at 05:34:15PM -0400, Theodore Ts'o wrote:
> On Wed, Oct 31, 2012 at 12:06:19PM +0100, Dave Martin wrote:
> > 
> > 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.
> 
> What I was suggesting was even more light-weight.  Just include at the
> very beginning or the very end of the the file the last time the
> translation was updated, and either the kernel version (i..e, v3.6) or
> the git commit ID (i.e., df981d03eeff) that was used for the source
> document.
> 
> That way, someone who reads the file will know how "fresh" the
> document is, and the reader can do a "git log -p
> Documentation/arm/kernel_user_helpers 1234567890abcd.." to see all of
> the changes made to the file since the last time the translation was
> updated.
> 
> People will inevitably remember to forget to notify the translation
> maintainers, and as the number of translations go up, the more
> workload we put on the everyone else.  If we simply mark the
> translation, then the translators can poll to refresh the document at
> their leisure, or perhaps this allows anyone who is using the
> translated documentation file and who has a reasonable command of
> English to do the "git log -p ..." command and perhaps contribute a
> patch to update the translation.  So I think this approach would scale
> much better.

The only potential issue I see here is that the final commit ID may not
be known at least until the patch is applied in a maintainer tree.  But
I guess this is not a different problem from existing practices where a
patch references commit IDs.

It sounds like a reasonable, practical approach to me.

Cheers
---Dave

  reply	other threads:[~2012-11-01 14:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 16:20 Tekkaman Ninja
2012-10-30 19:03 ` Theodore Ts'o
2012-10-31 10:44   ` harryxiyou
2012-10-31 11:06   ` Dave Martin
2012-10-31 21:34     ` Theodore Ts'o
2012-11-01 14:23       ` Dave Martin [this message]
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=20121101142338.GA29971@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome