public inbox for gentoo-doc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Flammie Pirinen <flammie@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] [RFC] Marking unmaintained documents
Date: Fri, 30 Sep 2005 11:59:53 +0300	[thread overview]
Message-ID: <20050930115953.11905c57@pingviinilohhari> (raw)
In-Reply-To: <433C0B12.3000103@gentoo.org>

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

2005-09-29, Xavier Neys sanoi, jotta:

> Disclaimer & redirect
>    () Yea  () Nay

Nay for delayed redirect. It's confusing and causes only usability
problems. It's also proprietary kludge to HTTP protocol, which has
never been approved to standard for a good reason. Either use instant
redirect with proper HTTP headers or nothing at all. Having automatic
delayed redirect provides nothing useful. If the user misses the
disclaimer and starts reading the document instead he will be very
annoyed and confused when it suddenly disappears, if user sees the
disclaimer he will be perfectly capable of activating the link when he
has finished reading the disclaimer and not any time sooner or later.

> Note about more recent English version
>    () Yea  () Nay

Yay, of course.

-- 
Flammie, Gentoo Linux Documentation's Finnish head translator.
<http://dev.gentoo.org/~flammie>

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-09-30  9:00 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
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 [this message]
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=20050930115953.11905c57@pingviinilohhari \
    --to=flammie@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