From: Eli Zaretskii <eliz@gnu.org>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: 28607@debbugs.gnu.org
Subject: bug#28607: 27.0.50; help-fns unsolicited elisp loading
Date: Mon, 02 Jul 2018 21:16:34 +0300 [thread overview]
Message-ID: <83h8lhjyf1.fsf@gnu.org> (raw)
In-Reply-To: <CAKyxw10XCzp1fY96vcm_Ep_hZsF3a-YQeUnSkUc1p5WvPtDYhw@mail.gmail.com> (message from Mark Oteiza on Mon, 2 Jul 2018 14:05:14 -0400)
> From: Mark Oteiza <mvoteiza@udel.edu>
> Date: Mon, 2 Jul 2018 14:05:14 -0400
> Cc: Glenn Morris <rgm@gnu.org>, 28607@debbugs.gnu.org
>
> >> On 26/09/17 at 11:40am, Glenn Morris wrote:
> >> > Why did you close 28048 as fixed and open this new report?
> >> > It's the same thing.
> >>
> >> You're right. I should have just retitled the old report.
> >
> > As bug#28048 is marked "done", should this one be closed as well?
>
> No, as I wrote previously, it probably would have made more sense to
> retitle bug#28048.
So "it's the same thing" above is inaccurate or incorrect? (The title
doesn't bother me, only the essence.)
> Evidently this was ignored for the 26 release, so now I'm not sure
> what the point of blocking bugs is.
It wasn't ignored. But as no one seemed to want to pick up the
gauntlet, and since my assessment of the bug's severity was that it's
relatively minor, I saw no reason to block the release due to it.
next prev parent reply other threads:[~2018-07-02 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 12:49 bug#28607: 27.0.50; help-fns unsolicited elisp loading Mark Oteiza
2017-09-26 15:40 ` Glenn Morris
2017-09-26 15:51 ` Mark Oteiza
2018-07-02 17:57 ` Eli Zaretskii
2018-07-02 18:05 ` Mark Oteiza
2018-07-02 18:16 ` Eli Zaretskii [this message]
2018-07-03 1:29 ` Glenn Morris
2018-07-16 13:03 ` Mark Oteiza
2019-05-16 2:12 ` Noam Postavsky
2019-05-16 13:38 ` Eli Zaretskii
2019-05-18 16:00 ` Noam Postavsky
2019-05-18 16:15 ` Eli Zaretskii
2019-05-20 17:49 ` Noam Postavsky
2019-05-20 19:01 ` Eli Zaretskii
2019-05-21 11:45 ` Noam Postavsky
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=83h8lhjyf1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28607@debbugs.gnu.org \
--cc=mvoteiza@udel.edu \
/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.