all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Status of TODO remove obsolete bug-reporting commando
Date: Tue, 28 May 2019 08:13:06 -0400	[thread overview]
Message-ID: <jwvh89eokbk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: CADwFkm=d1TGMgLFWob0Ug8sq_c1pPxg7En_HTFLuhwHSOLNbXQ@mail.gmail.com

> I've been looking into the following TODO:

Thanks.

> The final question leaves the prospective contributor in some doubt. I
> think the first step is to clarify what it is that should be done.

I consider it to be the main step ;-)

> First: Do all of them need changing?

That's one half of the question.

> I was able to find the following commands that are *not* mentioned in
> the TODO:

That's the other half.

> - artist-submit-bug-report
> - ediff-submit-report
> - ps-mode-submit-bug-report
> - reftex-report-bug
> - vera-submit-bug-report
> - verilog-submit-bug-report
> - vhdl-submit-bug-report
> - viper-submit-report        [obsolete package]
>
> Should we also add them to the TODO, or is there a reason that they
> have not been included?

Because we noone had looked into it yet.

As for which ones to keep and which ones to remove, we can start by
removing all those where there is no maintainer any more (i.e. the
maintainer is "us").

For those where it's unclear, we should try and contact the maintainer
to see his opinion.  If you can't get an answer (typically because none
of the email addresses one can find work any more), then we can change
the maintainer to "emacs-devel@gnu.org" (but make sure the
non-answering previous maintainer is listed in "Author:", so we don't
lose track of his past role).

> Finally, the attached patch contains cleanups of things that already
> seems to be removed, for example the `report-calc-bug' command that
> has already been removed.

Thanks, looks good, installed,


        Stefan




      parent reply	other threads:[~2019-05-28 12:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-26 16:30 Status of TODO remove obsolete bug-reporting commando Stefan Kangas
2019-05-27 16:43 ` Alan Mackenzie
2019-05-28  7:56   ` Michael Albinus
2019-05-28 12:13 ` Stefan Monnier [this message]

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=jwvh89eokbk.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@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.