Timeline for Flag to close because the question is answered
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 12, 2017 at 18:16 | comment | added | TheWanderer | Also,it is completely acceptable to take a comment-answer and turn it into a full answer yourself. It's best if you either tell the person to make it an answer or at least give them a shout-out in your answer, but neither is necessary. Questions shouldn't be closed because they're answered. Even if one is accepted, adding an alternative answer can be helpful to others who have the same problem, especially if the accepted solution doesn't work for them. Same goes if the answer is in the comments or is unaccepted. | |
| Jan 12, 2017 at 15:37 | vote | accept | LinuxSailorTech | ||
| Jan 12, 2017 at 15:36 | comment | added | Byte Commander Mod | As I said, I voted to close that specific question with the described reason, because the commend said "Hello! For some reason the issue solved itself. My best guess would be that [...] Probably an issue related to [...]". It's a problem that "magically" went away. New answers would not make sense because the OP can no longer verify whether they would have helped and the comment itself is also not precise enough for an answer. | |
| Jan 12, 2017 at 15:30 | comment | added | LinuxSailorTech | Fair enough I suppose however there do seem to be quite a few of these sorts of questions floating around and I wondered if anything could be done about them for example (askubuntu.com/questions/815705/…) | |
| Jan 12, 2017 at 15:24 | history | edited | Byte CommanderMod | CC BY-SA 3.0 |
added 379 characters in body
|
| Jan 12, 2017 at 15:24 | history | edited | terdonMod | CC BY-SA 3.0 |
Fixed typo; included official reference
|
| Jan 12, 2017 at 15:21 | history | answered | Byte CommanderMod | CC BY-SA 3.0 |