From: Alexey Chumakov <achumakov@gmail.com>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] Re: [RFC] Marking unmaintained documents
Date: Mon, 19 Sep 2005 11:51:07 +0400 [thread overview]
Message-ID: <432E6DEB.7000007@gmail.com> (raw)
In-Reply-To: <loom.20050915T135454-193@post.gmane.org>
Xavier Neys пишет:
> Notes:
> 0) All languages must have a metadoc.xml. Not a problem IMO. <metadoc/> will do
> for currently unsupported languages.
> 1) We have to use metadoc and *may not* test the corresponding file (ie.
> s:/pl/:/en/:) as that would force us to keep files we want to remove in /doc/en/
> until all translated versions have disappeared.
> 2) We need to use the dates and not the versions because using the versions
> would force us to compare handbooks file by file.
> 3) Reminder: the date of a handbook is the max_date(master, all parts)
> 4) Some of you need to stop bumping dates needlessly
> 5) link attributes must contain the full path, no more <book
> link="handbook-x86.xml"> (not required on my test site, but would be on www.g.o)
>
> At the moment, it is limited to /doc as dates are not reliable outside of /doc
> anyway (not yyyy-mm-dd formatted or not bumped properly).
>
> Samples:
> http://gentoo.neysx.org/doc/fr/handbook/2005.1/
> http://gentoo.neysx.org/doc/pl/nvidia-guide.xml
>
> FYI, an inserts would like like
> http://gentoo.neysx.org/doc/en/inserts-en.xml?passthru=1
>
> Please comment.
>
As for me, it's good that we only give a hint -- it's up to our user to
decide if the doc is really obsolete.
Great solution Xavier!
WKR,
Alexey Chumakov
--
gentoo-doc@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-19 7:52 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 16:56 [gentoo-doc] [RFC] Marking unmaintained documents Jan Kundrát
2005-09-08 17:07 ` Xavier Neys
2005-09-08 17:36 ` Jan Kundrát
2005-09-08 17:54 ` Xavier Neys
2005-09-08 18:12 ` Jan Kundrát
2005-09-08 19:04 ` Shyam Mani
2005-09-09 17:00 ` Sven Vermeulen
2005-09-09 16:57 ` Sven Vermeulen
2005-09-10 13:10 ` Jan Kundrát
2005-09-10 18:22 ` Sven Vermeulen
2005-09-10 20:26 ` Jan Kundrát
2005-09-14 16:55 ` Sven Vermeulen
2005-09-14 18:20 ` Jan Kundrát
2005-09-08 21:00 ` Alexey Chumakov
2005-09-08 21:10 ` Jan Kundrát
2005-09-08 21:11 ` Łukasz Damentko
2005-09-09 1:13 ` Flammie Pirinen
2005-09-09 6:50 ` Alexey Chumakov
2005-09-09 13:10 ` Jan Kundrát
2005-09-09 13:08 ` Jan Kundrát
2005-09-09 15:49 ` Flammie Pirinen
2005-09-09 16:26 ` Łukasz Damentko
2005-09-10 13:11 ` Jan Kundrát
2005-09-09 16:50 ` Sven Vermeulen
2005-09-10 12:35 ` Jan Kundrát
2005-09-15 11:51 ` Xavier Neys
2005-09-15 11:55 ` [gentoo-doc] " Xavier Neys
2005-09-16 13:01 ` Jan Kundrát
2005-09-17 12:06 ` Sven Vermeulen
2005-09-19 7:51 ` Alexey Chumakov [this message]
2005-09-16 9:01 ` [gentoo-doc] " Xavier Neys
2005-09-16 13:07 ` Jan Kundrát
2005-09-16 15:24 ` Xavier Neys
2005-09-16 18:51 ` Jan Kundrát
2005-09-29 15:41 ` Xavier Neys
1980-01-03 20:09 ` Alexey Chumakov
2005-09-29 16:49 ` Jose Luis Rivero
2005-09-29 22:57 ` Łukasz Damentko
2005-09-30 7:20 ` Shyam Mani
2005-09-30 8:59 ` Flammie Pirinen
2005-09-30 16:29 ` Sven Vermeulen
2005-10-02 13:11 ` Jan Kundrát
2005-10-09 10:21 ` Xavier Neys
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=432E6DEB.7000007@gmail.com \
--to=achumakov@gmail.com \
--cc=gentoo-doc@lists.gentoo.org \
/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