Timeline for Allow post editor to see @comments directed at him
Current License: CC BY-SA 2.5
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 7, 2010 at 9:46 | comment | added | Jeff Atwood | @arjan that would be a little nuts. Talking to editors via comment is clearly useful in the case of bad retags or weird edits, however. | |
| May 7, 2010 at 9:00 | vote | accept | alex | ||
| May 7, 2010 at 8:53 | history | edited | Jeff Atwood |
edited tags
|
|
| Mar 15, 2010 at 9:46 | history | edited | Jeff Atwood |
edited tags
|
|
| Mar 15, 2010 at 6:16 | answer | added | Gnome | timeline score: 2 | |
| Mar 4, 2010 at 10:42 | comment | added | Arjan | In the duplicate "@comment notification and Editing" at meta.stackexchange.com/questions/41101/… @Koper takes it even one step further: It would be nice if it worked with every person who has been active in the question; including posting another answer, casting a close vote, editing, etc. (However, I don't think it should be taken that far.) | |
| Jan 18, 2010 at 7:31 | answer | added | Jeff Atwood | timeline score: 17 | |
| Jan 18, 2010 at 6:59 | comment | added | alex | @random I've seen a few questions that were edited beyond recognition, completely changing their meaning. People that notice these mistakes don't always have edit rights; notifying the original editor might prove useful. | |
| Jan 18, 2010 at 6:20 | comment | added | random | Especially if you've been on an edit spree and lose track of all your fine quality edits but happened to tag or typo just one of 25 of the posts. | |
| Jan 18, 2010 at 6:13 | history | asked | alex | CC BY-SA 2.5 |