Timeline for Character limit on Code Review
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jun 3, 2022 at 20:10 | history | notice added | MastMod | Obsolete | |
| S Jun 3, 2022 at 20:10 | history | locked | MastMod | ||
| Jan 8, 2017 at 10:25 | answer | added | Simon ForsbergMod | timeline score: 7 | |
| Jan 8, 2017 at 10:24 | history | edited | Simon ForsbergMod |
edited tags
|
|
| Nov 21, 2013 at 23:10 | history | edited | AdamMod |
edited tags
|
|
| Apr 23, 2013 at 21:49 | comment | added | Gareth Rees | On this site, good answers often need to be longer than the questions, so spare a thought for the answerers! (For example, here's an answer which I had trouble fitting into the 30,000 character limit.) | |
| Apr 23, 2013 at 6:13 | answer | added | AdamMod | timeline score: 8 | |
| Apr 23, 2013 at 2:33 | history | edited | Shog9StaffMod |
edited tags
|
|
| Apr 23, 2013 at 2:32 | history | migrated | from meta.stackexchange.com (revisions) | ||
| Apr 23, 2013 at 0:27 | comment | added | Polynomial | I'll +1 this since it seems like a good idea, with the caveat that all posts on Code Review should highlight the areas of code that are being focused upon. Posts containing little more than 3000 lines of code are always bad. | |
| Apr 23, 2013 at 0:23 | history | asked | adaam | CC BY-SA 3.0 |