[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: gufw problem

On 09/12/2015, Jape Person <japers@comcast.net> wrote:


> Just as a matter of etiquette for this mailing list, I thought I'd
> mention a couple of things.
> 1. It's best not to reply directly to another user's e-mail address --
> unless that user has specifically requested to be CC'd. Most people who
> post here subscribe to the list, so they will receive any response you
> make to the debian-user list. If you send to the list and to them, they
> get two copies of each message.
> Many mail clients and browser-based mail systems (like gmail) make it
> too easy to respond accidentally to a personal e-mail address instead of
> to the list address. It happens by accident all the time. But it's
> something you might want to avoid, if you can.

Simplest way to deal with this, when replying to a mailing list
message, is selecting the "Reply To All" option (in both gmail, and in
PINE/ALPINE), cutting the list email address from the CC field, and,
pasting it over (so as to replace) the email address of the poster of
the message to which the reply is being made.

It is always better, when a mailing list is configured, so that
replies default to the list, but, when that is not configured, I have
found the above method, to be the way to deal with it.

> 2. When replying, it's also usually considered best on this list (and on
> many other technical lists) to user interleaved reply format -- like the
> way I've been replying to you.

Also, I believe, named "Inline Posting".

"Top posting" - posting before the message to which a reply is made,
so as to cause absolute confusion as to what exactly, a person is
replying, and, so that people reading the message are not inclined to
read to what the reply is being made, so that the reply is read out of
context, so as to cause maximum confusion.

"Bottom posting" posting after the message to which the reply is made,
so that people who are reading the reply, if they are worth anything,
will read the message to which the reply is made, before reading the
reply that is made, so that the reply is read in the context of the
message to which the reply is made. This message is best, when the
reply is made to the whole of the message, rather than individual
replies to individual points within the message to which the reply is

"Inline posting" - where replies to individual points within a
message, are inserted immediately after the points to which the
individual replies are made. Very useful for that purpose.

"tolerance" - where people who use a different posting method , to
another person, and, tolerate the other person's method, even though
the person believes the person's method to be better and more

"bigotry" = intolerance of something that is different to the bigot -
where some bright spark decides to start a stupid argument about which
posting method should be applied, to the exclusion of all else (this
DOES NOT apply to the poster of the message above, who, to me, is
merely suggesting the contextual benefit of inline posting, rather
than dogmatically insisting that a particular method should be used
exclusively, simply because it is the way of a bigot)

These are simply my opinions and experience, and, others may have
different opinions, and, we should be tolerant of those who are
different to us, while, as above, suggesting (and, not insisting) what
may be a better implementation (although, some may say that what I
posted above, is, maybe, not so tolerant, but, I will not argue the
point, beyond what I have said here).


Bret Busby
West Australia


"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992


Reply to: