8

Recently I posted a ridiculously long question about a SerialPort issue. I chronicled the events in decent detail and after about a month of screwing up I finally found the issue and posted my answer on the now wiki'd question.

What I want to know is should I go through, summarize the issue and the answer and get rid of the rest of the 'non-essentials'? Some of the comments might not make as much sense and (maybe not in this case) sometimes the other answers don't make any sense if there is too much pruning.

What is the etiquette in this situation? Do I leave it as is? Or simplify it as much as possible? And what about other people's posts? Wiki posts? Thanks in advance!

1 Answer 1

12

I removed wiki from the question and your answer, since it's really not necessary there.

I suggest cleaning up the question to incorporate all the edits into a single, coherent description of what happened and your debugging steps. Then leave your solution ("curse you, firmware!") in your answer.

Comments can be flagged to be cleaned up as obsolete.

1
  • 1
    I will definitely add 'curse you firmware!' in my answer. I yelled it when I found out, the least I can do is share it with the coding world.
    – tmwoods
    Mar 19, 2013 at 20:32

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .