On 5/15/24 10:50, Nicolas George wrote:
Cindy Sue Causey (12024-05-15):
PS Afterthought is that email signatures are another of that widely
accepted netiquette set of standards.
You can add the “Re: ” to that list.
It is the sequence of four octets 0x52, 0x65, 0x3a, 0x20, and nothing
else.
of them.
. . .
Actually, it isn't necessarily the user's fault. Thanks to the "business
standard," (and think about the initials) of top-posting over the
complete, unpared quote of the entire thread, there are an awful lot of
email readers (and especially webmail interfaces) that make it
Since my request started this offtopic subthread I hope I can put it to
rest.
Yes I requested to not toppost. I asked politely, and I added pertinent
response on topic. I do not claim to be right or wrong about this. I prefer
interleaved style for reason. Everyone on this list heard all arguments
Cindy Sue Causey (12024-05-15):
> PS Afterthought is that email signatures are another of that widely
> accepted netiquette set of standards.
You can add the “Re: ” to that list.
It is the sequence of four octets 0x52, 0x65, 0x3a, 0x20, and nothing
else.
The MUAs who write “RE: ” are wrong.
On 5/15/24 10:06, Nicolas George wrote:
Cindy Sue Causey (12024-05-15):
Best as I was able to discern from the Net [0], 72 characters is the
magic number for line length because 4 extra characters are added to
both ends when e.g. git processes submissions. Makes good common sense
to me.
Git
On Wed, May 15, 2024 at 09:46:08AM -0400, Cindy Sue Causey wrote:
> Best as I was able to discern from the Net [0], 72 characters is the
> magic number for line length because 4 extra characters are added to
> both ends when e.g. git processes submissions. Makes good common sense
> to me.
>
> PS
-Original Message-
From: Greg Wooledge
To: debian-user@lists.debian.org
Subject: Re: OT: Top Posting
Date: 05/14/24 13:41:17
On Tue, May 14, 2024 at 05:01:31PM +, fxkl4...@protonmail.com wrote:
> how many times has this top post crap been dug up
> don't y'all have any thing
Cindy Sue Causey (12024-05-15):
> Best as I was able to discern from the Net [0], 72 characters is the
> magic number for line length because 4 extra characters are added to
> both ends when e.g. git processes submissions. Makes good common sense
> to me.
Git is an order of magnitude younger than
-Original Message-
From: gene heskett
To: debian-user@lists.debian.org
Subject: Re: OT: Top Posting
Date: 05/14/24 10:54:50
On 5/14/24 10:09, Richard wrote:
Just because something isn't an official ISO standard doesn't mean
it's
not standard behavior. And how it relates to this mailing
On 15/05/2024 02:32, Greg Wooledge wrote:
On Tue, May 14, 2024 at 08:16:20PM +0200, Nicolas George wrote:
Messages in Markdown in the Windows world? I have never seen it.
[...]
The only sensible interpretation I can
come up with for why these asterisks were added is that they're being
placed
>>>
>>> > Am Di., 14. Mai 2024 um 15:57 Uhr schrieb Loris Bennett
>>> > mailto:loris.benn...@fu-berlin.de>>:
>>> >
>>> > Hi Richard,
>>> >
>>> > Richard mailto:rrosn...@gmail.com>> writes:
>>>
On Tue, 14 May 2024, Andy Smith wrote:
> Hello,
>
> On Tue, May 14, 2024 at 05:01:31PM +, fxkl4...@protonmail.com wrote:
>> don't y'all have any thing better to do
>
> You must be new here.
sorta
i've only been using versions of linux since the early 90's :)
downloaded it from an archie
Hello,
On Tue, May 14, 2024 at 05:01:31PM +, fxkl4...@protonmail.com wrote:
> don't y'all have any thing better to do
You must be new here.
Get used to reading with a "mark thread read" key in your MUA of
choice, is my best advice.
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS
Greg Wooledge wrote:
> In this particular instance, we've got a person from the second
> culture who seems to have no idea that other cultures exist, or that
> a mailing list might not adhere to their own expectations. This
> person is acting belligerantly, and will not listen to gentle
>
On Tue, May 14, 2024 at 08:16:20PM +0200, Nicolas George wrote:
> Messages in Markdown in the Windows world? I have never seen it.
I can't be sure where they're coming from exactly, but every once in
a while I see messages on debian-user, bug-bash or help-bash which
have extra asterisk characters
ts cannot do that, its time to switch to an agent
>> that can. There are dozens of them.
>>
>> > Am Di., 14. Mai 2024 um 15:57 Uhr schrieb Loris Bennett
>> > mailto:loris.benn...@fu-berlin.de>>:
>> >
>> > Hi Richard,
>&g
the
software in between cannot take, i.e. most of it.
And the “(s)” tells us which culture is more efficient and why.
The second culture are Windows users who grew up with Microsoft products
in their school or workplace. In this culture, top-posting is the norm,
and inline quoting is nigh impossib
On Tue, May 14, 2024 at 05:01:31PM +, fxkl4...@protonmail.com wrote:
> how many times has this top post crap been dug up
> don't y'all have any thing better to do
> i know
> how about some real debian issues
>
Hi,
Have a quick look at the Debian-user FAQ posted each month and the
Debian
t.
And the “(s)” tells us which culture is more efficient and why.
> The second culture are Windows users who grew up with Microsoft products
> in their school or workplace. In this culture, top-posting is the norm,
> and inline quoting is nigh impossible. Messages are often sent in ei
On 5/14/24 10:41 AM, Greg Wooledge wrote:
We have a clash of two cultures here.
More than just *nix vs. M$.
In business communications by email, the norm is to quote the *entire*
thread, every time, without paring anything down, purely for the sake of
CYA. As such, top-posting is the only
on a
terminal, or a terminal emulator. Characters are displayed in a
fixed-width font. ASCII art is possible, albeit frowned upon as
juvenile.
The second culture are Windows users who grew up with Microsoft products
in their school or workplace. In this culture, top-posting is the norm,
and inli
how many times has this top post crap been dug up
don't y'all have any thing better to do
i know
how about some real debian issues
On Tue, May 14, 2024 at 04:08:19PM +0200, Richard wrote:
> Just because something isn't an official ISO standard doesn't mean it's not
> standard behavior. And how it relates to this mailing list? It's called a
> setting.
Most people prefer inline quoting around here (I know I do). That's
because
> > Hi Richard,
> >
> > Richard mailto:rrosn...@gmail.com>> writes:
> >
> > > "Top posting" (writing the answer above the text that's being
> replied
> > > to) is literally industry standard behavior.
> >
:rrosn...@gmail.com>> writes:
> "Top posting" (writing the answer above the text that's being replied
> to) is literally industry standard behavior.
Can you provide a link to the standard you are referring to?
Assuming such a standard exists, how would it apply t
Just because something isn't an official ISO standard doesn't mean it's not
standard behavior. And how it relates to this mailing list? It's called a
setting.
Am Di., 14. Mai 2024 um 15:57 Uhr schrieb Loris Bennett <
loris.benn...@fu-berlin.de>:
> Hi Richard,
>
> Richard wri
Hi Richard,
Richard writes:
> "Top posting" (writing the answer above the text that's being replied
> to) is literally industry standard behavior.
Can you provide a link to the standard you are referring to?
Assuming such a standard exists, how would it apply to this newsg
Hello,
On Thu, Jun 22, 2023 at 04:24:47PM -0700, Manphiz wrote:
> Personally I don't have a strong preference either way, but would like
> to hear more opinions on this.
The complaint about a top-posted forwarded message just because it
had a contextual hint at the top, seemed excessive to me. I
David Christensen writes:
> On 6/22/23 03:28, Ottavio Caruso wrote:
>> Am 21/06/2023 um 15:46 schrieb to...@tuxteam.de:
>
>>> ... top posting ...
>
>> ... When the message is forwarded ("Weitergeleitet", ... you have no
>> other choice
On Sun, 30 Aug 2020 09:14:16 -0700
Charlie Gibbs wrote:
> If someone can't be bothered to take the time to write a readable
> message, I can't be bothered to take the time to decipher it.
On the other tentacle, this sort of thing is usually the province of
newbies. I think it would help to
Charlie Gibbs composed on 2020-08-30 09:14 (UTC-0700):
> On Sun, 30 Aug 2020 16:30:01 +0200 Charles Curley wrote:
>> On Sun, 30 Aug 2020 14:02:48 + Andy Smith wrote:
>>> Between your top posting and the HTML mails, I find it very
>>> difficult to read your
On Sun, 30 Aug 2020 16:30:01 +0200
Charles Curley wrote:
> On Sun, 30 Aug 2020 14:02:48 +
> Andy Smith wrote:
>
>> Between your top posting and the HTML mails, I find it very
>> difficult to read your emails so I mostly haven't bothered.
>
> Hear, hear. My se
gt;> >> otros de otra.
> >> >>
> >> > No, no es la forma natural ¿o tú respondes antes que te hagan una
> >> > pregunta? ¿o respondes antes que te hablen?
> >> >
> >> > Saludos.
> >> >
> >> >
>
blen?
> >
> > Saludos.
> >
> >
> Lo concidero la forma natural porque es una respuesta a algo ya leido,
> muy diferete a la cominicación hablada, imagina hablando antes de
> respoder repetir todo lo ya dicho
>
La verdad no se te entiende mucho, pero no es natural
El 18/9/19 a las 18:10, Felix Perez escribió:
El mié., 21 de ago. de 2019 a la(s) 13:55, juan
(juansanti...@riseup.net) escribió:
No sabía que en esta lista hay un regla anti top-postng por eso lo hacía
siempre, para mi es la forma natural de responder para mi es muy fácil seguir
un hilo si
cesibilidad.
>
Tal y como cuando un usuario señala que se le envía copia al privado,
el usuario podría solicitar que se le conteste con top posting.
Saludos.
> Yo, personalmente, soy editor de la Wiki Debian; tengo los permisos
> necesarios; cosa que no es difícil de hacer, pero tambi
El mié., 21 de ago. de 2019 a la(s) 13:55, juan
(juansanti...@riseup.net) escribió:
>
> No sabía que en esta lista hay un regla anti top-postng por eso lo hacía
> siempre, para mi es la forma natural de responder para mi es muy fácil seguir
> un hilo si se que tengo que hacerlo de abajo a
On Tue, Sep 10, 2019 at 6:40 PM Jaime Casanova
wrote:
>
> Sin embargo, el hacerlo así no es una cuestión de debian por ejemplo
> en el rfc 1855 (https://www.ietf.org/rfc/rfc1855.txt) se incluye este
> párrafo:
> """
> - Be brief without being overly terse. When replying to a message,
>
, aunque así lo parece en realidad Debian como muchos otros
proyectos de software libre es una *meritocracia*.
>
> Siguiendo esta línea de razonamiento pongo sobre la mesa la siguiente
> discusión:
>
> La regla de Top Posting y Bottom-Posting fue establecida en un tiempo en que
>
>
Hola
A mi personalmente me da lo mismo Top-posting o Bottom Posting. Lo que
creo es que las normas se pueden modificar, no estamos en una
dictadura,pero esa modificación debe ser por acuerdo entre todos y que
esa norma acordada la cumplamos todos, y no como hasta ahora que unos
hacen t
El jue., 22 ago. 2019 a las 6:17, Debian ()
escribió:
> Sí.
> Nosotros, los propios usuarios, con un acuerdo, podemos modificar las
> normas.
> Son normas de convivencia, no leyes escritas en piedra bajadas desde lo
> alto.
>
> Lo que habla Fran, invidente, es algo que debe incorporarse en las
>
Sí.
Nosotros, los propios usuarios, con un acuerdo, podemos modificar las
normas.
Son normas de convivencia, no leyes escritas en piedra bajadas desde lo
alto.
Lo que habla Fran, invidente, es algo que debe incorporarse en las
normas. No se me había pasado siquiera por la mente.
Podemos
:50, Fran Torres escribió:
>
> Buenas,
>
> yo siempre suelo hacer incapié en la accesibilidad (como usuario
> invidente de debian). De hecho, si no me equivoco, en la lista
> debian-accessibility (también estoy en ella) se utiliza mucho el
> top-posting. Por qué?
> Por que
la lista
debian-accessibility (también estoy en ella) se utiliza mucho el
top-posting. Por qué?
Por que con lectores de pantalla, es mucho más sencillo, rápido y
eficiente, leer la última respuesta como la primera. la penúltima como
la segunda y así sucesivamente. Es decir, top-posting.
A demás, si
Buenas,
yo siempre suelo hacer incapié en la accesibilidad (como usuario
invidente de debian). De hecho, si no me equivoco, en la lista
debian-accessibility (también estoy en ella) se utiliza mucho el
top-posting. Por qué?
Por que con lectores de pantalla, es mucho más sencillo, rápido y
"Asunto", agregando al
final la palabra "solucionado", así:
Re: OT Top-posting y Bottom Posting - [SOLUCIONADO]
|Y la respuesta directa a un ||usuario||creo que la mayoría la
||consideramos||improcedente, ||creo que mailman pude bloquear esta
posibilidad siempre que los corr
|No sabía que en esta lista hay un regla anti top-postng por eso lo
hacía siempre, para mi es la forma natural de responder para mi es muy
fácil seguir un hilo si se que tengo que hacerlo de abajo a arriba, pero
lo más importante es que nos pongamos de acuerdo, ya que el verdadero
desbarajuste
Top Posting y Bottom-Posting fue establecida en un tiempo en
que la mayoría de los usuarios Debian usábamos clientes sólo texto por
su versatilidad, rapidez y muchas otras cosas que en su tiempo superaban
a cualquier cliente gráfico. Sin embargo a más de una década desde
entonces, además del
mayor base
tecnológica de nuestros tiempos, se ha convertido en un ejemplo de lo que
una organización democrática bien organizada puede lograr.
Siguiendo esta línea de razonamiento pongo sobre la mesa la siguiente
discusión:
La regla de Top Posting y Bottom-Posting fue establecida en un tiempo en
Kenneth Parker writes:
> I have a special issue: Using Gmail on a Phone or Tablet (I have
> both).
Both of those devices lack a proper keyboard. That makes them unsuitable
for composing anything but very short messages, and wholly unsuitable
for editing text.
> Seriously, how do others of you
computer. Using an inferior tool
is no excuse to inconvenience others. My pet peeve here is when people
try to use the Stack Exchange app or whatever, and excuse the lousy
formatting on "I'm on the phone", but thanks for pointing out another
one: gmail top posting! It's bad enough in an a
On Thu, Sep 13, 2018 at 10:07 PM Ric Moore wrote:
>
>
>
> Same reason some people top post. They just ignore the conventions.
>
I have a special issue: Using Gmail on a Phone or Tablet (I have both). I
have yet to find a Straightforward way to Snip lots of lines, using the
Android App.
? ;-3)
Only if the situation calls for it. This one did :)
And the best place for a friendly advice about top-posting is at the
top.
Reco
http://lists.alioth.debian.org/pipermail/d-community-offtopic/2013-November/000303.html
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
On Thu, 21 Nov 2013 11:08:41 +1100
David bouncingc...@gmail.com wrote:
On 21 November 2013 10:31, Brad Alexander stor...@gmail.com wrote:
I'm just curious why so many people get so upset about top posting.
When you're curious about anything, use a search engine, like I used
to find
Kelly,
On a related note, something is wrong with your MUA and quoting. Here's
a section of the quoting from your last message, with an additional
layer of quoting applied, and trimmed to 20 characters (to avoid further
wrapping issues):
I'm just curious
so upset about top p
mind, as
David Guntner da...@guntner.com wrote:
GMail Yahoo Mail both support encrypted POP3 IMAP [...] I don't
have to look at their ads since I'm not using their web interface [...]
How long do you think it's going to be before they start inserting ads
into the message body then? (And/or offering a
I'm just curious why so many people get so upset about top posting. To my
mind, as threads get longer, those keeping up with the thread would not
want to scroll through messages that they have already read. I know that I
don't. If they are commenting inline, that is fine, but I think
The usual objection to top posting is that it destroys the logical
flow of the conversation (and no doubt someone will post a
conversation in reverse order to illustrate the point). But I agree
with you, and for years read my email in reverse chronological order
precisely so that I could save time
On Wed, Nov 20, 2013 at 3:40 PM, Patrick Wiseman pwise...@gmail.com wrote:
The usual objection to top posting is that it destroys the logical
flow of the conversation (and no doubt someone will post a
conversation in reverse order to illustrate the point). But I agree
with you, and for years
Brad Alexander grabbed a keyboard and wrote:
I'm just curious why so many people get so upset about top posting. To my
mind, as threads get longer, those keeping up with the thread would not
want to scroll through messages that they have already read. I know that I
don't
to top posting is that it destroys the logical
flow of the conversation (and no doubt someone will post a
conversation in reverse order to illustrate the point). But I agree
with you, and for years read my email in reverse chronological order
precisely so that I could save time getting
On 21 November 2013 10:31, Brad Alexander stor...@gmail.com wrote:
I'm just curious why so many people get so upset about top posting.
When you're curious about anything, use a search engine, like I used
to find this for you:
https://en.wikipedia.org/wiki/Posting_style
Especially
On Wed, Nov 20, 2013 at 3:40 PM, Patrick Wiseman pwise...@gmail.com wrote:
The usual objection to top posting is that it destroys the logical
flow of the conversation (and no doubt someone will post a
conversation in reverse order to illustrate the point).
snip
On Wed, Nov 20, 2013 at 6
On 11/20/2013 06:31 PM, Brad Alexander wrote:
I'm just curious why so many people get so upset about top posting. To
my mind, as threads get longer, those keeping up with the thread would
not want to scroll through messages that they have already read. I know
that I don't
On Wed, Nov 20, 2013 at 6:59 PM, David Guntner da...@guntner.com wrote:
Brad Alexander grabbed a keyboard and wrote:
I'm just curious why so many people get so upset about top posting. To my
mind, as threads get longer, those keeping up with the thread would not
want to scroll through
Brad Alexander grabbed a keyboard and wrote:
Actually, I can see the point of posting inline, however, leave it to
google and other mail apps to go and ruin it. In the gmail web interface,
when you reply to an email or even a thread, you get the text entry box,
with the message you are
-community-offtopic] Outrageous sexism - dump questions -
carbon copy - ignoring hidden ids - HTML - top posting - brainstorming -
etc.
Date: Thu, 22 Nov 2012 12:06:26 +0100
Is there anything people are else allowed on Debian user mailing list,
besides dissing people for harmless jokes, breaking
On Thu, Nov 22, 2012 at 12:14:19PM +0100, Ralf Mardorf wrote:
snip
All off-topic is caused by people who feel offended by harmless jokes,
breaking threads, asking the wrong questions, carbon copy, brainstorming
etc., not by the people who make harmless jokes, are breaking threads,
asking the
Hola
Si me dieran 1 centavo por cada vez que leo lo del top-posting, los
correos en html y los privados en la lista no tendría problemas
financieros por el resto de mi vida :)
Las normativas de la lista son claras al respecto:
1- Evitar el uso de HTML
2- Evitar el top-posting
3- Evitar los
Walber Zaldivar Herrera escribió:
Hola
Si me dieran 1 centavo por cada vez que leo lo del top-posting, los
correos en html y los privados en la lista no tendría problemas
financieros por el resto de mi vida :)
Las normativas de la lista son claras al respecto:
1- Evitar el uso de HTML
2
On Mar 01 Dic 2009 14:16:16 JAP escribió:
Walber Zaldivar Herrera escribió:
Hola
Si me dieran 1 centavo por cada vez que leo lo del top-posting, los
correos en html y los privados en la lista no tendría problemas
financieros por el resto de mi vida :)
Las normativas de la lista son
Estimados nuevos (o newbies, si prefieren el inglés).
Son todos bienvenidos a hacer cualquier tipo de pregunta en esta lista,
siempre y cuando vuestras preguntas cumplan estos requisitos:
Se note que hayan leído las “netiquettes”, o normas de convivencias. Si
no lo hicieron, háganlo en
JAP escribió:
Y por si a alguien le queda dudas,
http://download.bblug.usla.org.ar/netiquette.png
JAP
Jajajajajajajajajajajajajaja :) :) :)
s...@lu2
Walber
--
JHS/o
+-===|
(o_
//\Linux Registered User
V_/_ #480598
() ascii ribbon campaign - against html e-mail
/\
--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
2009/3/30, santilin sa...@gestiong.org:
--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
wikipedia es tu amiga ;)
http://es.wikipedia.org/wiki/Top-posting
http://es.wikipedia.org/wiki/Env
santilin escribió:
Top-posting es contestar arriba del mensaje respondido en vez de abajo,
cosa que hace incómoda la lectura:
http://es.wikipedia.org/wiki/Top-posting
Cross-posting es preguntar lo mismo en varias listas, lo que ocasiona
cierta mescolanza cuando alguien responde:
http
2009/3/28 Chris Jones cjns1...@gmail.com
On Fri, Mar 27, 2009 at 05:48:10AM EDT, Chris Bannister wrote:
I was asking one of the top-posting advocates to elaborate on archaic
mail readers .. written in the 1980s .. I believe he wrote..
I would assume he is not using one himself
confusing. :o
So in that situation I was happier[2] seeing a silly top posting
message.
[2] Only because I didn't have to press space a dozen or so times.
As you use mutt, 'S' should skip to the end of each section of quoted
text, or, if you know there is no interleaved quoting, just press
On Fri, Mar 27, 2009 at 05:48:26AM EDT, Chris Bannister wrote:
On Mon, Mar 23, 2009 at 06:11:38PM -0400, Chris Jones wrote:
Now then.. I have two bottom posters .. and one top poster..
OK.
What do I do?
Snip out the irrelevant bits. Do you use vim as your editor? If so you
can put a
is using if you put in your .muttrc:
I was asking one of the top-posting advocates to elaborate on archaic
mail readers .. written in the 1980s .. I believe he wrote..
I would assume he is not using one himself .. but then who knows..
-
# What headers are displayed
ignore *
unignore From
On Sun, Mar 22, 2009 at 01:04:54PM -0500, John Hasler wrote:
Chris Bannister wrote:
Bottom posting of course is just as bad or worse than top posting.
No. You obviously should middle post as I have done here: find the median
line and insert your comments is the center of it, splitting
On Sun, Mar 22, 2009 at 10:43:28AM -0700, Robert Holtzman wrote:
On Mon, 23 Mar 2009, Chris Bannister wrote:
Bottom posting of course is just as bad or worse than top posting.
Then, of course, it follows that not posting at all is ideal.
I *should* have said:
Without triming bottom posting
On Mon, Mar 23, 2009 at 06:08:35PM -0400, Chris Jones wrote:
What mailer are you referring to? I use mutt and it threads messages
reliably, flagging malformed mails that it adds to a thread when it
You can see what mailer he is using if you put in your .muttrc:
-
# What headers are
On Mon, Mar 23, 2009 at 06:11:38PM -0400, Chris Jones wrote:
Now then.. I have two bottom posters .. and one top poster..
OK.
What do I do?
Snip out the irrelevant bits. Do you use vim as your editor? If so you
can put a number before the 'dd' command: 40dd will delete 40 lines.
--
Chris.
On Sun, Mar 22, 2009 at 11:40:14AM -0500, Ron Johnson wrote:
On 2009-03-22 11:45, Chris Bannister wrote:
Bottom posting of course is just as bad or worse than top posting.
The only person who can say that with a straight face is one who has
spent too much time using Windows.
Or who reads
On 2009-03-24 07:06, Chris Bannister wrote:
On Sun, Mar 22, 2009 at 11:40:14AM -0500, Ron Johnson wrote:
On 2009-03-22 11:45, Chris Bannister wrote:
Bottom posting of course is just as bad or worse than top posting.
The only person who can say that with a straight face is one who has
spent
top posting
message.
[2] Only because I didn't have to press space a dozen or so times.
As you use mutt, 'S' should skip to the end of each section of quoted
text, or, if you know there is no interleaved quoting, just press the
'End' key to go right to the bottom ;-)
--
Bob Cox. Stoke
in that situation I was happier[2] seeing a silly top posting
message.
[2] Only because I didn't have to press space a dozen or so times.
As you use mutt, 'S' should skip to the end of each section of quoted
text, or, if you know there is no interleaved quoting, just press the
'End' key
Christofer C. Bell wrote:
On Mon, Mar 23, 2009 at 9:48 AM, Barclay, Daniel dan...@fgm.com
mailto:dan...@fgm.com wrote:
Christofer C. Bell wrote:
Mail 1: Q: What is the most annoying thing in e-mail?
Mail 2: A: Top-posting.
Mail 3: Q: Why is top-posting such a bad
is just as bad or worse than top posting.
The only person who can say that with a straight face is one who has
spent too much time using Windows.
--
Ron Johnson, Jr.
Jefferson LA USA
Freedom is not a license for anarchy.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
On Sunday 22 March 2009 23:07:29 Dave Patterson wrote:
* Boyd Stephen Smith Jr. b...@iguanasuicide.net [2009-03-22 20:34:50 -0500]:
That's hyperbole, at the very least. The original Pentium was released on
March 22, 1993. 3 1/2 disks had been available for a while. While the
first GB disk
Christofer C. Bell wrote:
On Sun, Mar 22, 2009 at 11:40 AM, Ron Johnson ron.l.john...@cox.net
mailto:ron.l.john...@cox.net wrote:
On 2009-03-22 11:45, Chris Bannister wrote:
...
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting
Chris Jones wrote:
On Sun, Mar 22, 2009 at 01:51:31PM EDT, Florian Kulzer wrote:
[..]
I need to see the relevant context quoted (properly trimmed as the
discussion progresses, of course), especially if a thread has run for
a while.
Most business mail runs something like this:
-
On Mon, Mar 23, 2009 at 9:48 AM, Barclay, Daniel dan...@fgm.com wrote:
Christofer C. Bell wrote:
Mail 1: Q: What is the most annoying thing in e-mail?
Mail 2: A: Top-posting.
Mail 3: Q: Why is top-posting such a bad thing?
Mail 4: A: Because it messes up the order in which people
In 143f0f6c0903230837k4d6bc8a5r55fe985e82993...@mail.gmail.com, Christofer
C. Bell wrote:
What is the most annoying thing in e-mail?
What is the most annoying thing in e-mail?
Top-posting.
What is the most annoying thing in e-mail?
Top-posting.
Why is top-posting such a bad thing?
What
On Mon, Mar 23, 2009 at 10:57:09AM EDT, Barclay, Daniel wrote:
Chris Jones wrote:
On Sun, Mar 22, 2009 at 01:51:31PM EDT, Florian Kulzer wrote:
[..]
I need to see the relevant context quoted (properly trimmed as the
discussion progresses, of course), especially if a thread has run
On Mon, Mar 23, 2009 at 10:37:21AM -0500, Christofer C. Bell wrote:
On Mon, Mar 23, 2009 at 9:48 AM, Barclay, Daniel dan...@fgm.com wrote:
Christofer C. Bell wrote:
Mail 1: Q: What is the most annoying thing in e-mail?
Mail 2: A: Top-posting.
Mail 3: Q: Why is top-posting
On Mon, Mar 23, 2009 at 12:16:12PM EDT, Boyd Stephen Smith Jr. wrote:
In 143f0f6c0903230837k4d6bc8a5r55fe985e82993...@mail.gmail.com, Christofer
C. Bell wrote:
[..]
Thank goodness my threaded mail reader never shows 4 messages at once.
(Alright, alright, it *can* but it doesn't do so for
. Manners or No Manners; it's an easy choice.
Bottom posting of course is just as bad or worse than top posting.
The only person who can say that with a straight face is one who has
spent too much time using Windows.
Now then.. I have two bottom posters .. and one top poster..
What do I
1 - 100 of 637 matches
Mail list logo
