From: Stefan Kangas <stefan@marxist.se>
To: "João Távora" <joaotavora@gmail.com>,
"Lars Ingebrigtsen" <larsi@gnus.org>
Cc: 42777@debbugs.gnu.org
Subject: bug#42777: 28.0.50; Obsolete eldoc-message function used in CEDET
Date: Tue, 1 Sep 2020 11:57:49 -0700 [thread overview]
Message-ID: <CADwFkmkHeku8RMvyJvg0UppQTFz1b1BR+OnGrkgQQgVdRRp2bg@mail.gmail.com> (raw)
In-Reply-To: <87zh69pdb8.fsf@gmail.com>
João Távora <joaotavora@gmail.com> writes:
> That's my view as well. So what's missing perhaps is that we close this
> bug and open another bug, as was Stefan Kangas' suggestion, to track the
> integration work. WDYT? Or maybe we should just leave this bug as that
> record, since it's where all the investigation done so far is
> registered anyway.
I don't have any strong feelings about it, but I think we could keep
this bug report as is.
My main concern was that this piece of information would be buried in a
long sub-thread of an unrelated issue. But that doesn't seem to be the
case here if obsoleting that file is indeed the solution we're going for.
next prev parent reply other threads:[~2020-09-01 18:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 15:23 bug#42777: 28.0.50; Obsolete eldoc-message function used in CEDET Lars Ingebrigtsen
2020-08-28 17:55 ` Stefan Kangas
2020-08-28 22:32 ` João Távora
2020-08-30 13:46 ` Lars Ingebrigtsen
2020-08-30 13:54 ` João Távora
2020-08-30 13:58 ` Lars Ingebrigtsen
2020-08-30 14:10 ` João Távora
2020-08-30 14:23 ` João Távora
2020-08-30 14:56 ` Stefan Kangas
2020-08-30 15:46 ` Lars Ingebrigtsen
2020-08-30 16:00 ` João Távora
2020-08-30 16:01 ` Lars Ingebrigtsen
2020-08-30 19:22 ` João Távora
2020-09-01 14:14 ` Lars Ingebrigtsen
2020-09-01 18:22 ` João Távora
2020-09-01 18:57 ` Stefan Kangas [this message]
2020-09-01 23:43 ` João Távora
2020-09-02 13:38 ` Lars Ingebrigtsen
2020-09-02 18:46 ` João Távora
2020-09-04 2:23 ` Lars Ingebrigtsen
2021-07-06 15:21 ` Lars Ingebrigtsen
2020-08-30 14:27 ` 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=CADwFkmkHeku8RMvyJvg0UppQTFz1b1BR+OnGrkgQQgVdRRp2bg@mail.gmail.com \
--to=stefan@marxist.se \
--cc=42777@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=larsi@gnus.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).