Hi, Same question here.
B. Le 15 déc. 2010 à 12:49, Ashley Taylor a écrit : > Hi, > > Does anyone have any decent filter rules for Gmail so I can stop receiving > this nonsense without unsubscribing? > > Thanks. > > On Wed, Dec 15, 2010 at 9:13 AM, Davide Mirtillo <dav...@ser-tec.org> wrote: > Il 15/12/2010 08:46, Dörfler Andreas ha scritto: > > > >>>>> > > To the rest of you....what is wrong with you? > > If you don't want to help, don't. Stop wasting time. Did it ever ocur to > > you that not everyone out there likes using a search engine? I was directed > > to debian-security by an ex-colleague since one of our servers uses debian. > > So I used it to ask a question that wasn't exactly related to security > > (although if you must know, it stemmed from another discussion on > > debian-security that did relate to security and one of my concerns was the > > version number of my system). So what? The responses I've received from you > > make me feel like I've committed a crime against humanity! > > <<<< > > > > dear ash, > > > > well, isn't that a basic problem inside the web community? > > i see it nearly every day: > > > > "use google" > > "use the search function" > > "my parents failed at breeding, and my education stopped since kindergarten" > > > > ppl out there so damn bored about their daily life, they have nothing > > better todo then to troll and flame others because of a "stupid question" > > (there are no stupid questions (mostly), only stupid answers) - that way > > they can prove their supreme intelligence (<- thats sarcasm, google wiki > > for it ... ). > > > > i tell my "real life" friends to google for problems from time to time too, > > but thats because they are just to lazy (mostly windows users ;-)). > > > > i think it's ok to tell ppl to user google, but in the same time: tell them > > the answer to their questions too. > > search engines are based on search tags, when someone searches with the > > "wrong" words, it can take hours to find an answer. > > > > maybe i will ask a "stupid apache question" this week, be ready for impact! > > Please, stop crying about it. I hate people who do that. They're either > fundamentally lazy or just 13 years old kids who like to troll on the > internet. > > I'll go ahead and explain to you why giving you an answer to such a > simple question has generated some harsh responses, by quoting one of > the most useful how-to that i've come across: > > > > Before asking a technical question by e-mail, or in a newsgroup, or on a > > website chat board, do the following: > > > > 1.Try to find an answer by searching the archives of the forum you plan > > to post to. > > 2.Try to find an answer by searching the Web. > > 3.Try to find an answer by reading the manual. > > 4.Try to find an answer by reading a FAQ. > > 5.Try to find an answer by inspection or experimentation. > > 6.Try to find an answer by asking a skilled friend. > > 7.If you're a programmer, try to find an answer by reading the source > > code. > > > > When you ask your question, display the fact that you have done these > > things first; this will help establish that you're not being a lazy sponge > > and wasting people's time. Better yet, display what you have learned from > > doing these things. We like answering questions for people who have > > demonstrated they can learn from the answers. > > > > Use tactics like doing a Google search on the text of whatever error > > message you get (searching Google groups as well as Web pages). This might > > well take you straight to fix documentation or a mailing list thread > > answering your question. Even if it doesn't, saying “I googled on the > > following phrase but didn't get anything that looked promising” is a good > > thing to do in e-mail or news postings requesting help, if only because it > > records what searches won't help. It will also help to direct other people > > with similar problems to your thread by linking the search terms to what > > will hopefully be your problem and resolution thread. > > > > Take your time. Do not expect to be able to solve a complicated problem > > with a few seconds of Googling. Read and understand the FAQs, sit back, > > relax and give the problem some thought before approaching experts. Trust > > us, they will be able to tell from your questions how much reading and > > thinking you did, and will be more willing to help if you come prepared. > > Don't instantly fire your whole arsenal of questions just because your > > first search turned up no answers (or too many). > > > > Prepare your question. Think it through. Hasty-sounding questions get hasty > > answers, or none at all. The more you do to demonstrate that having put > > thought and effort into solving your problem before seeking help, the more > > likely you are to actually get help. > > > > Beware of asking the wrong question. If you ask one that is based on faulty > > assumptions, J. Random Hacker is quite likely to reply with a uselessly > > literal answer while thinking “Stupid question...”, and hoping the > > experience of getting what you asked for rather than what you needed will > > teach you a lesson. > > > > Never assume you are entitled to an answer. You are not; you aren't, after > > all, paying for the service. You will earn an answer, if you earn it, by > > asking a substantial, interesting, and thought-provoking question — one > > that implicitly contributes to the experience of the community rather than > > merely passively demanding knowledge from others. > > > > On the other hand, making it clear that you are able and willing to help in > > the process of developing the solution is a very good start. “Would someone > > provide a pointer?”, “What is my example missing?”, and “What site should I > > have checked?” are more likely to get answered than “Please post the exact > > procedure I should use.” because you're making it clear that you're truly > > willing to complete the process if someone can just point you in the right > > direction. > > I strongly suggest you to read the whole thing, i'm sure that it will be > a good thing for you. > > Here's the link: > http://www.catb.org/~esr/faqs/smart-questions.html > > Have a good day. > > -- > Davide Mirtillo > EV Network, Via Emilio Salgari 14/e > 31056 Roncade (TV), Italy > http://evnetwork.it > > > -- > To UNSUBSCRIBE, email to debian-security-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/4d0886a8.3060...@ser-tec.org > >
