Skip to main content

Timeline for Short answers and code-only answers

Current License: CC BY-SA 3.0

10 events
when toggle format what by license comment
Jun 10, 2020 at 13:09 history edited CommunityBot
Commonmark migration
Apr 13, 2017 at 12:41 history edited CommunityBot
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
Jan 28, 2014 at 21:29 comment added Jamal Mod Ideally, an answer should only be flagged with a custom message if it should be deleted or converted to a comment. If it's not a non-answer, but just an answer that's factually incorrect (where a downvote would be best), it shouldn't be flagged, otherwise it will be rejected.
Jan 28, 2014 at 21:10 history edited Simon Forsberg CC BY-SA 3.0
added 160 characters in body
Jan 28, 2014 at 21:08 comment added Simon Forsberg @ChrisW For those without privileges to down-vote, vote to delete and/or handle flags; Flagging answers is the only option left. So of course flagging is OK. For users who have the privileges but are not entirely sure, flagging and/or discussing on chat/meta is a viable option.
Jan 28, 2014 at 21:01 comment added ChrisW That's why this meta-post exists: to discuss a flagged answer, where I didn't know whether I should agree with the flag. I was inclined to agree with the flag if "no code-only" was an agreed policy, otherwise inclined to disagree with the flag.
Jan 28, 2014 at 20:47 comment added Simon Forsberg @ChrisW See the edit. Technically, it usually doesn't hurt to flag a post. Flagging posts at least brings it to attention and if users have different opinions then it will likely be discussed in chat, in comments, and/or on meta.
Jan 28, 2014 at 20:45 history edited Simon Forsberg CC BY-SA 3.0
added flagging information
Jan 28, 2014 at 20:37 comment added ChrisW So in summary, I think you're saying downvote but don't flag code-only answers. And, usually flag link-only answers; but other short answers may be fine.
Jan 28, 2014 at 19:36 history answered Simon Forsberg CC BY-SA 3.0