From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "30491-done@debbugs.gnu.org" <30491-done@debbugs.gnu.org>
Subject: bug#30491: [External] : Re: bug#30491: 26.0; (elisp) `Profiling'
Date: Sat, 23 Oct 2021 11:36:37 -0700 [thread overview]
Message-ID: <CADwFkm=4P64G7=YtoaDxg3gYfPU+aGShku-QAFrqY8VqPMEP_w@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB5488A9E5F927CBCCEE5DABDBF3819@SJ0PR10MB5488.namprd10.prod.outlook.com>
Drew Adams <drew.adams@oracle.com> writes:
>> From reading this thread, it seems like the documentation issues here
>> have been fixed. There were also some tangents, but separate bug
>> reports were filed for those. So it doesn't seem like there's nothing
>> more to do here, and I'm closing this bug.
>>
>> As always, please report back if there's something I missed. Please
>> open new bug reports for any remaining issues that are not related to
>> the documentation changes discussed here. Thanks in advance.
>
> Some doc problems were addressed; other problems (UI)
> were not. (The bug wasn't closed in 2018, BTW.)
The fact that the bug wasn't closed doesn't tell us much, as bugs are
routinely left open for over a decade around here just because someone
forgot to close it. ;-)
If I understand you correctly, you are saying that there are outstanding
UI issues left to fix. I suggest you open new bug reports for them, as
it takes a significant amount of time to trawl through bug reports about
unrelated issues looking for such nuggets of information. As is
evidenced by me closing this bug: I didn't see that there was anything
in here that wasn't already fixed, even after having read the discussion
in full.
Thanks in advance.
next prev parent reply other threads:[~2021-10-23 18:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<d0e242c5-d77b-407e-a2a9-f60b3a48fcef@default>
[not found] ` <<837ercc4mp.fsf@gnu.org>
2018-02-17 15:45 ` bug#30491: 26.0; (elisp) `Profiling' Drew Adams
2018-02-17 16:16 ` Noam Postavsky
2018-02-17 16:24 ` Eli Zaretskii
2018-02-18 17:36 ` Drew Adams
2018-02-20 18:26 ` Drew Adams
2021-10-23 17:01 ` Stefan Kangas
2021-10-23 18:18 ` bug#30491: [External] : " Drew Adams
2021-10-23 18:36 ` Stefan Kangas [this message]
2021-10-23 19:06 ` Drew Adams
2021-10-23 19:14 ` Eli Zaretskii
2021-10-23 19:38 ` Drew Adams
2021-10-24 5:49 ` Eli Zaretskii
2021-10-23 21:13 ` Stefan Kangas
2021-10-23 19:12 ` Eli Zaretskii
2018-02-18 15:52 ` Drew Adams
2018-02-18 16:22 ` Drew Adams
2018-02-16 18:11 Drew Adams
2018-02-16 18:15 ` Drew Adams
2018-02-17 10:06 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkm=4P64G7=YtoaDxg3gYfPU+aGShku-QAFrqY8VqPMEP_w@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=30491-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).