public inbox for gentoo-doc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jan Kundrát" <jkt@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] [RFC] Marking unmaintained documents
Date: Thu, 08 Sep 2005 20:12:08 +0200	[thread overview]
Message-ID: <43207EF8.3040102@gentoo.org> (raw)
In-Reply-To: <43207AF2.5060800@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

Xavier Neys wrote:
>> This implies manual changing of several files which is not good, IMHO.
> 
> 
> Why? We change a small number of docs once, then forget about them.
> Do you think it is better to introduce more code, more complexity to be
> maintained, more stuff to be executed on each and every doc request?
> Is that your definition of better?

I'm not familiar with inner workings of gorg/axkit and I don't know
anything about speed issues or expensiveness of XML transformations, sorry.

> If we mark some files as unmaintained, we're also telling our users that
> non-marked files *are* maintained.

Good point, but IMHO we are now telling that *everything* is maintained
("file is on gentoo.org -> it's official").

> You should try to think about feasibility, implementation & consequences
> first.

That's why I included "[RFC]" in the subject. I don't know if it is
possible and worth the effort, I'm just asking.

Cheers,
-jkt

-- 
cd /local/pub && more beer > /dev/mouth

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2005-09-08 18:13 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 [this message]
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
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=43207EF8.3040102@gentoo.org \
    --to=jkt@gentoo.org \
    --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