Ok here are my explanations. Upon a re-read of what I typed up, it doesnt really sound all that coherent but I think we've beaten this horse long enough. Im not angry, nor should I be. this was a misunderstanding; in my hast I offended and ...well who cares, its over now. Here is my type up.
***
There are many aspects to consider here--and I will by no means cover them all but I will try to hit on some of the major ones--and im not really going to spend a whole lot of time explaining either (Im just going to say it and let you draw our own conclusions).
First a quote from the link provided in PM.
Use meaningful, specific subject headers
On mailing lists, newsgroups or Web forums, the subject header is your
golden opportunity to attract qualified experts' attention in around
50 characters or fewer. Don't waste it on babble like ``Please help
me'' (let alone ``PLEASE HELP ME!!!!''; messages with subjects like
that get discarded by reflex). Don't try to impress us with the depth
of your anguish; use the space for a super-concise problem description
instead.
One good convention for subject headers, used by many tech support
organizations, is ``object - deviation''. The `object' part specifies
what thing or group of things is having a problem, and the `deviation'
part describes the deviation from expected behavior.
Stupid:
HELP! Video doesn't work properly on my laptop!
Smart:
X.org 6.8.1 misshapen mouse cursor, Fooware MV1005 vid. chipset
Smarter:
X.org 6.8.1 mouse cursor on Fooware MV1005 vid. chipset - is
misshapen
The process of writing an `object-deviation' description will help you
organize your thinking about the problem in more detail. What is
affected? Just the mouse cursor or other graphics too? Is this
specific to the X.org version of X? To version 6.8.1? Is this specific
to Fooware video chipsets? To model MV1005? A hacker who sees the
result can immediately understand what it is that you are having a
problem with and the problem you are having, at a glance.
More generally, imagine looking at the index of an archive of
questions, with just the subject lines showing. Make your subject line
reflect your question well enough that the next guy searching the
archive with a question similar to yours will be able to follow the
thread to an answer rather than posting the question again.
If you ask a question in a reply, be sure to change the subject line
to indicate that you're asking a question. A Subject line that looks
like ``Re: test'' or ``Re: new bug'' is less likely to attract useful
amounts of attention. Also, pare quotation of previous messages to the
minimum consistent with cluing in new readers.
Do not simply hit reply to a list message in order to start an
entirely new thread. This will limit your audience. Some mail readers,
like mutt, allow the user to sort by thread and then hide messages in
a thread by folding the thread. Folks who do that will never see your
message.
Changing the subject is not sufficient. Mutt, and probably other mail
readers, looks at other information in the e-mail's headers to assign
it to a thread, not the subject line. Instead start an entirely new
e-mail.
On Web forums the rules of good practice are slightly different,
because messages are usually much more tightly bound to specific
discussion threads and often invisible outside those threads. Changing
the subject when asking a question in reply is not essential. Not all
forums even allow separate subject lines on replies, and nearly nobody
reads them when they do. However, asking a question in a reply is a
dubious practice in itself, because it will only be seen by those who
are watching this thread. So, unless you are sure you want to ask only
the people currently active in the thread, start a new one.
LINK: [
http://catb.org/~esr/faqs/smart-questions.html#intro ]
NOTE: Obviously not all that applies to us but most of the concepts are sound.Now what does that boil down to? Well, in more or less words, if [you] dont catch [my] attention with a subject line, I am not going to read the question. In fact, the only reason I entered this thread is because `poor subject lines' are kind of an annoyance of mine. And the less people you have reading your posts, the less help you get. Im not trying to seem conceded or anything, im just stating that most people dont bother reading unless they are ``involved'' somehow (``Oh, I know that one!'' or ``I'm good with that, I bet I can help.'').
This may seem like a reach, but theSwamp benefits too. We have an amazing group of people here. Ive read the posts on many forums and seen many questions. I dont think there is much we havent already or can not answer. we have Professional, Student, and Amateur programmers here. Providing quick accurate answers helps to prove that theSwamp is the place to go, the best and only place.
One more.
I classify this one under the ``wasted time/effort'' classification; If im not sure of the problem, I have to ask that many more return questions in an effort to understand. where if I can act upon and test predetermined conceptions with a properly worded subject line/question I can (hopefully) get your problem solved right away (first response).
Okay, there are tons of excuses/reasons and we can be here all day listing and discussing them but I think that is enough for now.
If an when you get time, read that link. It is a very good read.
