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


Hi Michael, all

Michael Meeks schrieb:

On Tue, 2011-02-15 at 13:54 +0800, David Nelson wrote:
Sure. Why don't you start a new thread then and, with your first post,
CC to michael.meeks@novell.com so that he sees it. I'm sure he'll post
back.

        Sounds good to me; the only problem is the mind-mashed reply-to
mangling on this list, that not only encourages people to post more -
since they don't get duplicate personal replies to threads ;-) but also
means that my CC will inevitably be lost - so in this thread, I only got
your (CC'd) mail, not Matt's reply.

        Hey ho - list mis-configuration is one of those evil nasties I'd love
to fix from the Collabnet monster; it helps build community. We have it
done 'right' for the dev list at least ;-)

Not for me personally - I always forget to "reply all" and I don't see any reason to get every mail twice. I think the dev list does it wrong ;-)

If you are involved in a thread, just mark it and you'll can easily get notice on every new mail in this thread - no need for personal CC or double mails.

So definition of "right" is not that easy as you suppose...

Best regards

Bernhard

--
Unsubscribe instructions: E-mail to website+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/website/
*** All posts to this list are publicly archived for eternity ***

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.