Edit - Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Rev

Late answers are not "by def'n" first posts. Is it the case that only questions that are also first posts make it into the "late answer" queue though? If so then this should be made precise; if not, corrected.
– djechlin
Commented May 17, 2013 at 22:18
See meta.stackexchange.com/a/177553/147247 - late answers are from "new users" which while not quite as strict as First Posts, is "close to that" - you or I cannot post "Late Answers" by the definition of the queue.
– Kate Gregory
Commented May 18, 2013 at 20:56
Possible typo: 2nd line of #1 -- should "to an old answer" be "to an old question"?
– fixer1234
Commented Jul 16, 2017 at 4:55
Any recommended way to deal with this post, encountered in the "Late Answers" review queue? stackoverflow.com/questions/52419840/…
– Adrian Mole
Commented Oct 18, 2019 at 14:12
3

The scenario I see most frequently with the Late Answers queue are duplicate answers. These aren't obviously plagiarized; instead, I just assume a new user saw the question, knew the answer, and quickly posted it without first reading the existing answers. These obviously aren't contributing meaningfully to the thread, but they don't otherwise violate the guidelines. What's the best way to handle these scenarios? So far, I've been leaving comments reminding the contributor to read the existing answers before submitting their own, but then marking them as Looks OK.
– Jeremy Caney
Commented May 7, 2020 at 0:42

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>

formatting help »
answering help »