X-Debbugs-CC: Eli Zaretskii <e...@gnu.org>, Michael Albinus <michael.albi...@gmx.de> Package: bugs.debian.org
Hello, This bug report is originated from a discussion in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61490 The web page displays the following metadata about the bug report: GNU bug report logs - #61490 [PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵ Previous Next Package: emacs; Reported by: Konstantin Kharlamov <Hi-Angel <at> yandex.ru> Date: Mon, 13 Feb 2023 20:01:02 UTC Severity: normal Tags: patch Merged with 61489 Done: Eli Zaretskii <eliz <at> gnu.org> Bug is archived. No further changes may be made. To add a comment to this bug, you must first unarchive it, by sending a message to control AT debbugs.gnu.org, with unarchive 61490 in the body. You can then email your comments to 61490 AT debbugs.gnu.org in the normal way. Toggle the display of automated, internal messages from the tracker. View this report as an mbox folder, status mbox, maintainer mbox However, The meaning of Merged with 61489 Done: Eli Zaretskii <eliz <at> gnu.org> Bug is archived. No further changes may be made. is rather specific to debbugs and may need to be clarified for new users. In particular, it is not very clear if the bug is "Done", archived, or merged - three different states in popular forges. Now, after some input from more experienced users, I do know that "merged" implies that several bugs share their state. But it is not obvious at all without reading the documentation. Would it be possible to add a link to documentation explaining the bug status workflow somewhere near the bug summary web page? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
