Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


On 05/02/2014, Felmon Davis <davisf@union.edu> wrote:

That doesn't mean they can't/shouldn't learn.

I wholly concur that top-posting is a scourge and especially if the
post is not trimmed; sometimes I just skip posts since I cannot figure
out what in the long tail of to and fro the poster is referring and
replying to, esp top-posted one-liners that make no sense. it's just
not worth it.


True

and Tom's post here is irrelevant to the issue why one _should_
bottom-post, trim and put comments in-line but he provides valuable
understanding of the forces against the practice.


The majority >90% posts are irrelevant...

I don't see that we all will come to agreement so that cannot be the
point of these discussions. I think we could give them some point if
the one side would provide a succinct summary of what it considers
good reasons for top-, and the other side provides good reasons for
bottom-posting.

at least that would or can shed light on the issues and lessen the
heat. maybe.


You're dreaming; each to their own.

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.