From: Andrew Hyatt <ahyatt@gmail.com>
To: John Wiegley <jwiegley@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: hanche@math.ntnu.no, 1452@debbugs.gnu.org
Subject: bug#1452: Acknowledgement (23.0.60; Problem with nextstep, longlines-mode,)
Date: Tue, 05 Jan 2016 21:12:19 +0000 [thread overview]
Message-ID: <CAM6wYYJ+bfDuyF1aJDJERJTzXUrqMjOiOwtdbGPWRSbuE-3+EQ@mail.gmail.com> (raw)
In-Reply-To: <m27fjnwymn.fsf@newartisans.com>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
On Tue, Jan 5, 2016 at 3:38 PM John Wiegley <jwiegley@gmail.com> wrote:
> >>>>> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> It's in lisp/obsolete/.
> >> Eli thinks such things should still be fixed:
>
> > Unless the fix is complicated or risky or...
>
> If people want to fix bugs in lisp/obselete, they are free to do so because
> (a) the bug is open and (b) the code still exists in the distribution. Once
> the code is gone, we can close the bug as no longer pertaining to Emacs.
>
Has anyone considered putting these obsolete packages in the gnu ELPA? I'm
not sure about the bug policy, but I'd guess that bugs shouldn't be filed
against ELPA packages.
>
> Until that time, don't feel an obligation to fix bugs in obsolete code that
> you aren't interested in fixing. There are higher priorities to address.
>
Perhaps we can lower the priority of these kinds of bug in that case to the
minimum, so it doesn't show up in the default list for debbugs?
>
> What this discussion objected to (as I read it) was establishing a policy
> of
> ignoring bugs in obsolete code.
>
> --
> John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
> http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
>
[-- Attachment #2: Type: text/html, Size: 2041 bytes --]
next prev parent reply other threads:[~2016-01-05 21:12 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 [this message]
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
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=CAM6wYYJ+bfDuyF1aJDJERJTzXUrqMjOiOwtdbGPWRSbuE-3+EQ@mail.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.