Bob DeBolt wrote: > On Wed December 13 2006 2:00 am, you wrote: > > Hi Andreas > >> Please, pretty please, don't hijack a thread by just changing the >> subject-line. > > I'm not aware of any existing thread regarding logical disk rates, I have > all > the list emails since August 15th. I did a number of word searches on them > and > didn't find any emails that thing fit the description of what I'm trying to > do. Likewise google. Is it a recent / existing thead ? > > Pass on a date?? >
That's not what I meant. You chose a random message from the list, hit the "reply" button, edited the subject line and removed all the message contents, and then filled in your message and sent it. This is what is considered "hijacking" a thread (the original thread was "[Nagios-users] Using $ in password"). Doing this means that everyone who sort messages by thread and aren't interested in how to use '$' in passwords will not see your message, because it will be buried inside the original thread. For the people who *are* interested in the previous thread, your hijacking of it only adds clutter to "their" thread. As for *this* mail, it was addressed to me directly, which is almost always inappropriate for list discussions and quite often considered rude unless explicitly asked for (I'm bringing it back on-list btw). -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null