2

I have seen that users ask questions related to code and, when they get solution to their current problem, they just make those changes to code in current question itself and change the question asking their next problem. This makes the already given answers irrelevant to the current question.

So is there any way to mark such questions? I just commented that its better to add a new question than editing same question.

7
  • @Servy: That's not quite the same thing. – user102937 Mar 10 '14 at 19:22
  • this is an interesting question. But i'm not sure people want to edit versus ask a new fresh Q . Snce visibility drops a lot . Hmm , Ok I can see why they might, to stretch the 7-question cap – Caffeinated Mar 10 '14 at 19:23
  • It seems like a good match to me, @RobertHarvey, but maybe you'd prefer Rolling back a completely changed question – jscs Mar 10 '14 at 19:25
  • I rolled back that question to a revision that makes sense for the current answers and left a comment for the OP – rene Mar 10 '14 at 19:26
  • @JoshCaswell: I would. – user102937 Mar 10 '14 at 19:26
  • Maybe a comment cleanup is also adviceable stackoverflow.com/questions/22308433/… – rene Mar 10 '14 at 19:27
  • @rene thanks. got it a person with privileges can roll back the question and leave a comment to OP. – LearningC Mar 10 '14 at 19:33
3

Someone with editing privileges should roll the post back to its previous revision. Question askers should not be changing the code in their question unless they made an error posting the actual code they were having a problem with.

If they insist on editing to ask a new question, vote to close the question as "problem can no longer be reproduced."

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