From: William Hubbs <williamh@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT:netiquete] was AUTO: Martin...
Date: Tue, 28 Apr 2009 13:03:43 -0500 [thread overview]
Message-ID: <20090428180343.GA8275@linux1> (raw)
In-Reply-To: <20090428191218.3b4ebcb9@ilievnet.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
All,
I don't normally get involved in these threads, but I want to point out
another reason for top posting.
As a blind computer user, sometimes it is more convenient to top post,
because I don't know of a way to make my screen reading software skip
over all of the quoted material. I find it more convenient sometimes to
hear the newest material first.
William
On Tue, Apr 28, 2009 at 07:12:18PM +0300, Daniel Iliev wrote:
> On Tue, 28 Apr 2009 16:51:41 +0100
> AllenJB <gentoo-lists@allenjb.me.uk> wrote:
>
> > The problem is that there's no consensus. I top post because I think
> > it's much more sensible. Others think otherwise. I live with it.
> >
> > It's the people who refuse to live with differences of opinion that
> > are the real problem.
> >
> > AllenJB
> >
>
>
> It's your choice weather to stay rfc-ignorant and "different".
> I shall follow the recommendations of IETF then yours.
>
>
> RFC 1855, Section 3.1.1:
>
> "If you are sending a reply to a message or a posting be sure you
> summarize the original at the top of the message, or include just
> enough text of the original to give a context."
>
>
> http://tools.ietf.org/html/rfc1855
>
>
> --
> Best regards,
> Daniel
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
iEYEARECAAYFAkn3RP8ACgkQblQW9DDEZTiMbwCglO03DGm25fY5iwxi8EO+gNuW
75oAn0vzSe7SiHNhsSVuNfrxOogPwTbC
=n40v
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-04-28 18:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 10:14 [gentoo-user] AUTO: Martin Schrodi ist außer Haus Martin Schrodi
2009-04-28 12:02 ` Daniel de Oliveira
2009-04-28 14:58 ` KH
2009-04-28 15:17 ` AllenJB
2009-04-28 15:30 ` Volker Armin Hemmann
2009-04-28 15:43 ` Neil Bothwick
2009-04-28 15:51 ` AllenJB
2009-04-28 16:08 ` Volker Armin Hemmann
2009-04-28 16:14 ` Saphirus Sage
2009-04-28 16:12 ` [gentoo-user] [OT:netiquete] was AUTO: Martin Daniel Iliev
2009-04-28 18:03 ` William Hubbs [this message]
2009-04-28 18:39 ` Neil Bothwick
2009-04-28 18:51 ` Marc Meyer
2009-04-28 18:59 ` Volker Armin Hemmann
2009-04-28 20:46 ` Neil Bothwick
2009-04-28 19:00 ` Alan McKinnon
2009-04-28 19:18 ` Dale
2009-04-28 19:26 ` thomas blomme
2009-04-28 19:31 ` Ward Poelmans
2009-04-28 19:36 ` Paul Hartman
2009-04-28 19:38 ` thomas blomme
2009-04-28 19:45 ` Dale
2009-04-28 20:05 ` Dirk Heinrichs
2009-04-28 20:45 ` Dale
2009-04-29 16:02 ` Dirk Heinrichs
2009-04-28 19:47 ` Volker Armin Hemmann
2009-04-28 20:04 ` Daniel de Oliveira
2009-04-28 20:16 ` Alan McKinnon
2009-04-28 20:25 ` Volker Armin Hemmann
2009-04-28 20:26 ` [gentoo-user] " Grant Edwards
2009-04-29 21:09 ` [gentoo-user] " Daniel Barkalow
2009-04-28 21:02 ` William Hubbs
2009-04-28 23:24 ` Neil Bothwick
2009-04-29 1:08 ` [gentoo-user] " Moshe Kamensky
2009-04-29 11:05 ` Willie Wong
2009-04-29 13:24 ` Willie Wong
2009-04-29 21:17 ` [gentoo-user] " Daniel Barkalow
2009-04-29 21:48 ` William Hubbs
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=20090428180343.GA8275@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-user@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