all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: 62479@debbugs.gnu.org
Subject: bug#62479: Missing bug tracker
Date: Mon, 27 Mar 2023 17:02:22 +0300	[thread overview]
Message-ID: <83355q9tsh.fsf@gnu.org> (raw)
In-Reply-To: <3a74bb6f7ff55653ac8bafa9febdb51b@posteo.de> (c.buhtz@posteo.jp)

tags 62479 notabug
thanks

> Date: Mon, 27 Mar 2023 08:42:36 +0000
> From: c.buhtz@posteo.jp
> 
> Hello,
> 
> I can not find a issue/bug tracker where I can subscribe to and monitor 
> specific bugs.

Please read the node "Bugs" in the Emacs user manual, it describes
this in detail.

> I assume you use the mailing list only?

No.  But email sent to bug-gnu-emacs@gnu.org is automatically directed
to our bug tracker, which registers new issues if necessary.  This is
described in short in INSTALL.REPO.

> This is not helpful for users or possible contributors. I want to 
> monitor specific bugs and not all bugs. But I need to keep subscribe to 
> the bug-mailinglist when I want to monitor bugs.

The discussion of bugs that you submit should normally keep you on the
CC list, so that you are informed about any such discussions.  You can
also review the status by pointing your Web browser to

   https://debbugs.gnu.org/cgi/bugreport.cgi?bug=NNNNN

where NNNNN is the bug number.





  parent reply	other threads:[~2023-03-27 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  8:42 bug#62479: Missing bug tracker c.buhtz
2023-03-27 13:15 ` bug#62479: Acknowledgement (Missing bug tracker) GNU bug Tracking System
2023-03-27 14:02 ` Eli Zaretskii [this message]
2023-03-27 14:22   ` bug#62479: Missing bug tracker c.buhtz
2023-03-28 11:13     ` Michael Albinus
2023-03-28 11:14 ` bug#62479: closed (Re: bug#62479: Missing bug tracker) GNU bug Tracking System

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83355q9tsh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62479@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.