Timeline for What to do with error logs that contain source information in release builds?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 9, 2017 at 18:20 | vote | accept | CommunityBot | ||
| Jul 9, 2017 at 16:14 | history | edited | Arseni Mourzenko | CC BY-SA 3.0 |
added 3962 characters in body
|
| Jul 9, 2017 at 16:05 | history | edited | Arseni Mourzenko | CC BY-SA 3.0 |
added 3962 characters in body
|
| Jul 9, 2017 at 15:50 | comment | added | user277416 | I believe this answer covered everything, so thanks. Also to elaborate on the "too revealing" part, when you're a beginner these kind of decisions are met with self-doubt and it seemed really awkward to have that info readable in the binary. I was afraid of breaking some kind of unspoken-rule. | |
| Jul 9, 2017 at 15:28 | comment | added | Deduplicator | ... Let's hope the log contains an exact version as the first line so the line-numbers and file-names actually make sense... | |
| Jul 9, 2017 at 15:10 | history | answered | Arseni Mourzenko | CC BY-SA 3.0 |