Timeline for Revealing bug report considered answer?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:25 | history | edited | CommunityBot |
replaced http://askubuntu.com/ with https://askubuntu.com/
|
|
| Mar 20, 2017 at 10:32 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Apr 28, 2016 at 8:03 | vote | accept | AlwaysTalkingAboutMyDog | ||
| Apr 27, 2016 at 21:23 | comment | added | Braiam | I've voted to close, as the reporter of the bug informs that "his bug is fixed" and disengaged. If the asker has the same bug as the reporter, and his issue isn't fixed yet, he should open another bug report. | |
| Apr 27, 2016 at 16:06 | comment | added | terdon | @bodhi.zazen yes. As you know, I find the whole AU stance of not allowing bugs to be discussed here counter productive, but if we;re going to do that, we should be consistent about it. Since there is already a link between AU and Canonical, I think finding a way to directly close bug questions as "duplicates" of the relevant bug report would be the best solution. | |
| Apr 27, 2016 at 15:59 | comment | added | Panther | +1 to close + link to bug report in comments. Wish the close vote had a way of including link to bug report. | |
| Apr 27, 2016 at 14:31 | history | answered | terdon | CC BY-SA 3.0 |