Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-doc
Navigation:
Lists: gentoo-doc: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-doc@g.o, gentoo-doc@g.o
From: Matthew Summers <quantumsummers@g.o>
Subject: Re: Updated date in handbook
Date: Thu, 29 Dec 2011 08:35:48 -0600
On Thu, Dec 29, 2011 at 8:27 AM, Sven Vermeulen <swift@g.o> wrote:
> Hi guys,
>
> Something else I noticed is that we sometimes get questions in #gentoo or
> even #gentoo-doc about the "Updated" date of the Gentoo Handbook(s). Because
> of how things work, the displayed date on the handbook pages is always the
> one that is for the given file.
>
> In case of the index page, this is a somewhat old(er) version as the index
> page hardly changes. Yet that is the "Updated" version most people look at.
>
> Would it be okay if I updated doc-struct.xsl so that for handbooks, the
> updated version always matches the latest update?
>
> Other possibilities are:
> - On the index page, display the latest update, but on individual chapters,
>  keep the current used date
> - Don't touch anything and stop harassing me with your suggestions
>
>
>        Sven Vermeulen
>

Another option, although I hate to add it, would be always update the
date on the index page when anything gets updated. However that is
sort of silly. I support updating doc-struct.xsl

Cheers,
Matt
-- 
Matthew W. Summers
Gentoo Foundation Inc.


References:
Updated date in handbook
-- Sven Vermeulen
Navigation:
Lists: gentoo-doc: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Updated date in handbook
Next by thread:
Re: Updated date in handbook
Previous by date:
Updated date in handbook
Next by date:
Re: Updated date in handbook


Updated Apr 08, 2012

Summary: Archive of the gentoo-doc mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.