[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9290.1184361017@turing-police.cc.vt.edu>
Date: Fri, 13 Jul 2007 17:10:17 -0400
From: Valdis.Kletnieks@...edu
To: Stefan Richter <stefanr@...6.in-berlin.de>
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>, Theodore Tso <tytso@....edu>,
Rob Landley <rob@...dley.net>, leoli@...escale.com,
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,
kenistoj@...ibm.com, schwidefsky@...ibm.com,
heiko.carstens@...ibm.com, linux-doc@...r.kernel.org
Subject: Re: Documentation of kernel messages (Summary)
On Fri, 13 Jul 2007 15:25:49 +0200, Stefan Richter said:
> Alan Cox wrote:
> > 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)
>
> I've got the impression that whenever I saw a "last updated:" note in a
> documentation, this note was out of date.
RCS and SCCS let you stick stuff like $DATE and $VERSION into the source, so
it would be automagically replaced at checkin/checkout time. Not sure how
well that would work across a mesh of 'git pull' and 'git push' across trees. :)
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists