all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Cc: John Wiegley <johnw@newartisans.com>
Subject: ToDo list and bugtracker
Date: Fri, 06 Nov 2015 15:15:39 +0100	[thread overview]
Message-ID: <563CB60B.7020209@online.de> (raw)
In-Reply-To: <m24mgzhn96.fsf@newartisans.com>

  On 06.11.2015 03:31, John Wiegley wrote:
>
> I'd love for someone to take care of our under-appreciated components.

+1
>   The
> TODO list right now is largely the bugtracker. Would you be willing to comb
> through some of the older reports, and find those bugs that no longer
> reproduce, or help resolve those that have patches needing review? Such a role
> would be extremely helpful.
>
> John
>

IMO that would require a joint effort at least of Hercules and Rübezahl. 
Because Emacs changed, older bugs aim at a fairly different state, thus 
real hard to re-track in many cases.

What about archiving old bugs after a certain time instead, so 
historiens might grab them if interested?

Cheers,

Andreas




  parent reply	other threads:[~2015-11-06 14:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 20:23 New Emacs maintainer John Yates
2015-11-03 20:33 ` John Wiegley
2015-11-03 20:44   ` Kaushal Modi
2015-11-03 20:45   ` John Yates
2015-11-03 22:02   ` David Kastrup
2015-11-04  7:58   ` Nicolas Petton
2015-11-04  8:34     ` Pierre Lecocq
2015-11-05  3:07   ` Karl Fogel
2015-11-05  5:12     ` John Wiegley
2015-11-06  2:27       ` Emanuel Berg
2015-11-06  2:31         ` John Wiegley
2015-11-06  3:26           ` Emanuel Berg
2015-11-06  4:14             ` Kaushal Modi
2015-11-06 14:15           ` Andreas Röhler [this message]
2015-11-06 21:40           ` Richard Stallman
2015-11-08 16:25             ` John Wiegley

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=563CB60B.7020209@online.de \
    --to=andreas.roehler@online.de \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@newartisans.com \
    /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.