linux-kernel - Re: Documentation of kernel messages (Summary)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070713134353.GB18684@thunk.org>
Date:	Fri, 13 Jul 2007 09:43:53 -0400
From:	Theodore Tso <tytso@....edu>
To:	Li Yang <leoli@...escale.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, Rob Landley <rob@...dley.net>,
	Gerrit Huizenga <gh@...ibm.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Kunai, Takashi" <kunai@...ux-foundation.jp>,
	holzheu@...ux.vnet.ibm.com,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	lf_kernel_messages@...ux-foundation.org, mtk-manpages@....net,
	jack@...e.cz, randy.dunlap@...cle.com, gregkh@...e.de,
	pavel@....cz, tim.bird@...sony.com, arjan@...radead.org,
	sam@...nborg.org, jengelh@...putergmbh.de, joe@...ches.com,
	auke-jan.h.kok@...el.com, hansendc@...ibm.com, davem@...emloft.net,
	Valdis.Kletnieks@...edu, kenistoj@...ibm.com,
	schwidefsky@...ibm.com, heiko.carstens@...ibm.com,
	linux-doc@...r.kernel.org
Subject: Re: Documentation of kernel messages (Summary)

On Fri, Jul 13, 2007 at 08:49:00PM +0800, Li Yang wrote:
> On Fri, 2007-07-13 at 11:53 +0100, Alan Cox wrote:
> > > One thing that would be a VERY good idea is to make sure that each
> > > translated document is tagged with when it was last translated, and
> > > against which kernel version (using either a GIT commit id or a
> > 
> > The English versions need a last updated too, that way we would know when
> > they are past their best before date (as most of them are)
> 
> Good idea.  So a "last updated" date field will be required for both the
> English and translated documents.  Date will be more straight forward
> than using commit id, IMHO.

Well, date and kernel version id, then.  Otherwise they may be
confusion if the translator is using 2.6.16.35 as opposed to
2.6.22-git3, etc.  I would hope that the translator would always be
using only the latest development branch, but I wouldn't want to
always bet on that.  One advantage of using git commit id is that
there's no question about what the source document version was for the
translation.  It also makes it easier for the translator since they
can just diff between the last git commit id, and HEAD, and then
update their translation accordingly.

							- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/