unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Merging or otherwise controlling one's own bugs on debbugs.gnu.org
@ 2023-09-27 20:46 Jens Schmidt
  2023-09-28  0:54 ` Visuwesh
  0 siblings, 1 reply; 2+ messages in thread
From: Jens Schmidt @ 2023-09-27 20:46 UTC (permalink / raw)
  To: emacs-devel

In 

  https://yhetil.org/emacs-bugs/87r0mj75ci.fsf@sappc2.fritz.box/

I tried to (force)merge my own bug to somebody else's using control
messages.  Which showed no visible result.  Then I tried to close it
with the additional fixed-in-version information:

  https://yhetil.org/emacs-bugs/87o7hn74nc.fsf@sappc2.fritz.box/

Again, without result.  (I finally closed it by sending to the
NNNNN-done@debbugs.gnu.org address.)

Was there anything syntactically wrong with these control messages?

Would there have been any difference if I sent them to the debbugs
control server, and not to NNNNN@debbugs.gnu.org?

Are such control messages reserved for list admins?

If yes, how would I request a change in bug status?

Is there any documentation on that topic except what is on

  https://debbugs.gnu.org/Emacs.html
  https://debbugs.gnu.org/Advanced.html

Thanks.



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-09-28  0:54 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-09-27 20:46 Merging or otherwise controlling one's own bugs on debbugs.gnu.org Jens Schmidt
2023-09-28  0:54 ` Visuwesh

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).