From: Glenn Morris <rgm@gnu.org>
To: 1452@debbugs.gnu.org
Subject: bug#1452: Acknowledgement (23.0.60; Problem with nextstep, longlines-mode,)
Date: Wed, 06 Jan 2016 13:16:49 -0500 [thread overview]
Message-ID: <pmpoxevai6.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAAF+z6E_DGAjyHfycosddp58J-uvvccK+QNaGPjCt7iWZaMuAQ@mail.gmail.com> (Xue Fuqiao's message of "Wed, 6 Jan 2016 16:28:45 +0800")
Bug reports for GNU Elpa packages are accepted on bug-gnu-emacs, so
moving a package there does not mean its reports can simply be closed.
Things are moved to obsolete/ when they are believed to be no longer
useful; either because a more modern replacement exists (as in this
case), or because few to no people are believed to be using whatever it
is any more.
For me, bugs in obsolete things go to the bottom of the bug pile.
Since the bottom of the pile will never be reached, this means they are
wontfix for me.
Files in obsolete/ may be deleted from Emacs at some point in the future.
In a tiny number of cases, where someone thinks that something that
would in obsolete/ could still be useful, and is willing to maintain it,
it has been copied to GNU Elpa, where it will live on after it gets
removed from Emacs. (Personally I doubt whether such packages will ever
see any significant updates, or users.)
(This is all off-topic for this report; perhaps this discussion could
continue elsewhere, if there is still stuff to say.)
prev parent reply other threads:[~2016-01-06 18:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 13:53 bug#1452: 23.0.60; Problem with nextstep, longlines-mode, Harald Hanche-Olsen
[not found] ` <handler.1452.B.122796683914175.ack@emacsbugs.donarmstrong.com>
2008-11-29 14:52 ` bug#1452: Acknowledgement (23.0.60; Problem with nextstep, longlines-mode,) Harald Hanche-Olsen
2008-11-29 15:11 ` Harald Hanche-Olsen
2016-01-05 4:10 ` Andrew Hyatt
2016-01-05 17:32 ` Glenn Morris
2016-01-05 17:39 ` Andrew Hyatt
2016-01-05 17:53 ` Harald Hanche-Olsen
2016-01-05 18:38 ` Eli Zaretskii
2016-01-05 18:29 ` Eli Zaretskii
2016-01-05 20:38 ` John Wiegley
2016-01-05 20:46 ` Eli Zaretskii
2016-01-05 21:15 ` Harald Hanche-Olsen
2016-01-05 21:12 ` Andrew Hyatt
2016-01-05 21:34 ` John Wiegley
2016-01-05 21:50 ` Dmitry Gutov
2016-01-06 1:47 ` Andrew Hyatt
2016-01-06 1:53 ` Dmitry Gutov
2016-01-06 3:45 ` Eli Zaretskii
2016-01-07 1:42 ` Andrew Hyatt
2016-01-07 1:58 ` Handling bugs in obsolete code (was: bug#1452: ...) John Wiegley
2016-01-07 3:27 ` Handling bugs in obsolete code Andrew Hyatt
2016-01-07 6:03 ` John Wiegley
2016-01-07 7:59 ` Glenn Morris
2016-01-07 8:28 ` CHENG Gao
2016-01-07 16:10 ` Eli Zaretskii
2016-01-07 18:17 ` John Wiegley
2016-01-07 3:42 ` bug#1452: Acknowledgement (23.0.60; Problem with nextstep, longlines-mode,) Eli Zaretskii
2016-01-07 3:54 ` Andrew Hyatt
2016-01-07 16:02 ` Eli Zaretskii
2016-01-06 8:28 ` Xue Fuqiao
2016-01-06 18:16 ` Glenn Morris [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=pmpoxevai6.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=1452@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.