hi shreyas, hi guenther. calm down, dudes. :-) i understand that it is time-saving to answer a question by shortly describing a possible way to solve the problem, i also do it that way most of the time, contrary to guenther explaining the background of the discussed behaviour. (my argumentation is that i'm able to answer *more* questions if i write a short answer, whilst guenther wants the people to understand the issue and to learn how stuff works(TM). i can fairly understand both approaches.) but i also second that it is important to add disclaimers in those cases where data could be harmed or destroyed. yes, the mail archives are public and one cannot expect anybody to read the entire thread from the beginning when he has just googled for an answer for his problem, so it's always a bit dangerous. (general comment and NOT refering to this thread:) if we're generally talking about style in gnome bugzilla and on this mailing list, i do recommend exact wordings (the UI terms that are used in evolution) and more helpful information (don't just tell the people "get a stacktrace", but tell them *how* to get one - a link to <http://www.gnome.org/projects/evolution>, section "debugging evolution's crashes", would already be enough). i've seen it quite a few times that data has been requested by developers without telling people *how* to get that data. so help the people to help themselves, but not to ask again or even try in a wrong way. be precise where necessary. cheers, andre -- mailto:ak-47 gmx net | failed! http://www.iomc.de
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil