| Summary: | Get rid of Gopher "support" | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | How can I remove my account? <tml> |
| Component: | LibreOffice | Assignee: | Adolfo Jayme Barrientos <fitojb> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | dennisroczek, librelegal, robinson.libreoffice, tml |
| Priority: | medium | Keywords: | difficultyBeginner, easyHack, skillCpp |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | target:4.5.0 | ||
| Crash report or crash signature: | Regression By: | ||
|
Description
How can I remove my account?
2015-02-13 09:59:59 UTC
Adolfo Jayme Barrientos committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=ea7f16bf0b5e195d65e51c624b0fb37980bf2b95 tdf#89361 Remove remnants of Gopher support It will be available in 4.5.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. This bug fix is mentioned in the release notes of the coming LibreOffice 5.0 (see release notes https://wiki.documentfoundation.org/ReleaseNotes/5.0). Therefore it would be wonderful if this feature really worked well, otherwise it should not be mentioned in the release notes. In the notes it reads: Vestigial Gopher Wikipedia logo v3.svg support was dropped as well. tdf#89361 Thanks to: Adolfo Jayme Barrientos. @ Mike §chinagl, it is pointless (not to mention annoying) to add that comment to every bug report you happen to see in the release notes. DO NOT DO THAT AGAIN. It doesn’t even apply in this case (“… if this feature really worked well”? WTF?) But if you’re really worried about testing the new features and bug fixes, what about you do the tests yourself, and move bugs to VERIFIED? (In reply to Adolfo Jayme from comment #3) > But if you’re really worried about testing the new features and bug fixes, > what about you do the tests yourself, and move bugs to VERIFIED? Maybe we need a clearer set of guidelines as some people active like you instruct user that only competent people should change the status of a bug (example: https://bugs.documentfoundation.org/show_bug.cgi?id=90511#c15). Migrating Whiteboard tags to Keywords: (EasyHack DifficultyBeginner SkillCpp ) [NinjaEdit] |