all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrew Hyatt <ahyatt@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: hanche@math.ntnu.no, jwiegley@gmail.com, 1452@debbugs.gnu.org
Subject: bug#1452: Acknowledgement (23.0.60; Problem with nextstep, longlines-mode,)
Date: Wed, 06 Jan 2016 22:54:30 -0500	[thread overview]
Message-ID: <m2fuyaoxhl.fsf@gmail.com> (raw)
In-Reply-To: <83k2nm2gyi.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 07 Jan 2016 05:42:29 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andrew Hyatt <ahyatt@gmail.com>
>> Date: Thu, 07 Jan 2016 01:42:58 +0000
>> Cc: jwiegley@gmail.com, rgm@gnu.org, hanche@math.ntnu.no, 1452@debbugs.gnu.org
>> 
>> what I'm mostly trying to figure out is if there is *any* way to get
>> code to be completely unmaintained.
>
> I think removing it is the only way.

Yeah, I guess that's what I suspected.  It seems reasonable, as long as
we can remove things.

>
>> We are, after all, trying to reduce the number of bugs (see the
>> thread on 4k bugs) overall, and this is one way to do that. So the
>> only way people would agree on right now, is if we remove the code
>> entirely from emacs distribution. But I suspect that such a change
>> would be rejected, even from obsolete packages, because someone
>> might still be depending on them.
>
> It depends on how long the package was obsolete, I guess.
>
> We could define a policy, like a package is deleted after so-and-so
> many months/years in obsolete/.

If you think such a policy would be possible, then I'm happy to propose
it in emacs-devel.  Maybe obsolete packages can spend one major version
in obsolete, and get deleted in the next major version?  Or, maybe we
can be more aggressive, especially if you think that we can do this over
periods of months, and obsolete and deprecate based on minor version instead.





  reply	other threads:[~2016-01-07  3:54 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 [this message]
2016-01-07 16:02                         ` Eli Zaretskii
2016-01-06  8:28                 ` Xue Fuqiao
2016-01-06 18:16                   ` Glenn Morris

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=m2fuyaoxhl.fsf@gmail.com \
    --to=ahyatt@gmail.com \
    --cc=1452@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=hanche@math.ntnu.no \
    --cc=jwiegley@gmail.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.