LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > LinuxQuestions.org > LQ Suggestions & Feedback
User Name
Password
LQ Suggestions & Feedback Do you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.

Notices


Reply
  Search this Thread
Old 12-18-2014, 07:59 PM   #1
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,442

Rep: Reputation: 76
Best way to get a prompt answer.


If you look at this post, you'll see the thread title is not very suggestive.

http://www.linuxquestions.org/questi...5/#post5287202

What do you think a suitable title for it could be?
 
Old 12-18-2014, 08:09 PM   #2
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,223

Rep: Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320
Your title is fine, and you did get a prompt response.
 
1 members found this post helpful.
Old 12-29-2014, 08:58 AM   #3
sundialsvcs
LQ Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 10,659
Blog Entries: 4

Rep: Reputation: 3941Reputation: 3941Reputation: 3941Reputation: 3941Reputation: 3941Reputation: 3941Reputation: 3941Reputation: 3941Reputation: 3941Reputation: 3941Reputation: 3941
There's a FAQ on this, but to me it comes down to just one thing: "consider the point-of-view of the potential responder, whose attentions you are (of course) trying to attract."

(1) Write a concise but meaningful title. I'm looking at a list of post titles right now ... and, years from now, someone else might be looking at titles, also. Therefore, make the title count. Don't say "I'm a newbie and I have a question." That's a waste of time and space. Instead, make the title be the post's first and most-important tag.

(2) Write an answerable question. The very first ¶ of the post should clearly express the question that you are asking, and should ask it in "answerable" terms. Subsequent paragraphs should contain supporting information. Source-code should be optional, stripped to the minimum necessary to express the problem, and enclosed in code-tags. The responder, having opened the thread based on the title, should immediately be able to comprehend your problem and what you have done or tried so-far. The responder, based on just this, ought to be able to now respond.

(3) Wait a reasonable amount of time. It might take a day or three for a response to arrive. Don't pester. If the thread doesn't get replies, consider appending another comment to the thread. This will cause it to re-appear in the list of "active threads."

(4) When the problem is satisfactorily resolved, mark the thread "[SOLVED]" and close the thread with a brief summary written by the original poster (OP). Briefly state what solved the problem, how you finally resolved it, and how you knew that the problem was solved. You're writing for the future person who, perhaps years from now and after you're pushing-up daisies (oops, too-bad about that bread truck, pal ...), will rediscover the thread.

(5) Don't "gut the thread." Don't remove the original content. Strikeouts are okay, as are "Update: ..." comments added after-the-fact to clarify "post #1," but don't eviscerate "post #1" even if you now feel about it. Once again, "remember future-person." The total thread, when finished and long-forgotten, should still be a complete and useful exchange meant to be durable for years to come. (It will be ...)
 
Old 12-29-2014, 10:36 AM   #4
jeremy
root
 
Registered: Jun 2000
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,602

Rep: Reputation: 4084Reputation: 4084Reputation: 4084Reputation: 4084Reputation: 4084Reputation: 4084Reputation: 4084Reputation: 4084Reputation: 4084Reputation: 4084Reputation: 4084
Two comments:

1) Your title was actually quite good.
2) You got a response that solved your issue in less than one hour. You may want to alter your definition of "prompt" in this context if you think one hour is too long. LQ is a 100% volunteer community with members spread over the globe.

--jeremy
 
1 members found this post helpful.
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
I can not find answer of this question. Please post helpful answer. pritammt Linux - Newbie 8 05-30-2014 05:43 AM
[SOLVED] Make Bash prompt look like Windows C:\ prompt -- *PROBLEM* arkadios Linux - General 5 07-24-2012 11:29 AM
[SOLVED] Automatically passing an answer to a command's prompt bret Linux - General 3 12-16-2011 09:01 AM
passing parameters from a unix shell prompt into a windows cmd.exe prompt nano2 Programming 1 09-01-2009 11:26 AM

LinuxQuestions.org > Forums > LinuxQuestions.org > LQ Suggestions & Feedback

All times are GMT -5. The time now is 07:20 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration