-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On Thursday 28 April 2016 at 10:02:30 AM, in <mid:CAO4LoOy26+qQfL8Bi_tNgp4jCbQitfgSL_Erz==zjoffazj...@mail.gmail.com>, Paolo Bolzoni wrote: > When you follow an email thyread you do not read > everything, you just > read the new email and it makes little difference if > it is in the top. Sometimes it makes a great deal of difference. Emails on mailing lists often arrive out of sequence, and some mailing list members may auto-delete messages from certain other members. The person reading your posting may not have seen the message that is being answered. Even if they have seen it, it may not be clear to which part of the message a top-posted comment refers. Bottom-posting is just as bad in this respect. > However, I agree there is not need to keep clutter > in the bottom of emails. Judicious quoting and inline quoting automatically precludes this. > So while I still don't see the big deal with > top-posting. For a list or organisation where top-posting is the norm, top-posting works despite its inefficiency. In fact, in such situations any other way of replying is liable to confuse. Where it is not the norm, it is confusing. It is a bit like driving on the wrong side of the road: either side is fine, as long as people do not try to mix them in the same location. > I agree that > is much better (A) to trim and answers to single > points or (B) simply > make a clean email. Please not (B), or it will appear as a new thread. (Unless you meant reply to the previous message without quoting from it.) - -- Best regards MFPA <mailto:2014-667rhzu3dc-lists-gro...@riseup.net> Keep them dry and don't feed them after midnight -----BEGIN PGP SIGNATURE----- iQF8BAEBCgBmBQJXIzfdXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2 QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXw5ogH/idg/fG6KQ5SVvaLYjcAIUC3 B7sFYOkpqNflq4eZ81JsZThfeYhn1vuGhhI/un3khaWKQ10azOmfwNRJCTlwoQBZ wSny+QYbLbsU3ZDt3VYPXTlhLb2aM6yrLRodmREhVuEMD9u8SK9DQmWegf+Q6BMa Vp62SbkbZwy+twsslHRy8XNIHFWJ4cBJvB7g01UR66G6nx2oBnxZGjCq9kFiUYu7 RI72UK2OUCzmf031KMppzUw/CPPcGzRsZ4vNkV266PfSboJlsZB68M5qaCnHTIlz UyTfTx6dgW4PIMXV1/6ajRni5CfK9Bd8TDx9DXTm2NqdRu+kkOuckV2jkqS8xvGI vgQBFgoAZgUCVyM33V8UgAAAAAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu cGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNBQ0VENEVFOTEzNEVFQkRFNkE4NTA2MTcx MkJDNDYxQUY3NzhFNAAKCRAXErxGGvd45F24AQCmn8Ur/JphfzdzaGFE+R4hw47K q6cHfK9cf13C1ZdzMAEA9/khkk4CSHnVGGw398b4otYe2LKCuTLSEE4Xp3GpjQY= =czj/ -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
