unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 52971@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#52971: Tests warn after eieio-compat.el was moved to obsolete/
Date: Fri, 14 Jan 2022 09:59:32 +0100	[thread overview]
Message-ID: <87lezipua3.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmnnXt0UzaHXtqeUaHNXUhcx0wBxG5vePRH0xFhWdwsUgg@mail.gmail.com> (Stefan Kangas's message of "Mon, 3 Jan 2022 11:48:51 -0500")

Stefan Kangas <stefan@marxist.se> writes:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> I'm not sure about the best way to fix them.  Could we just move those
>>> parts that require eieio-compat.el to a new file eieio-compat-tests.el?
>>
>> That will just move the warnings.
>
> My thinking was that if these tests are only for obsolete code, it would
> be better to isolate them all in one file.  But I have no real opinion
> either way.

I think isolating them in a new test file makes sense -- makes things
clearer.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2022-01-14  8:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03  1:29 bug#52971: Tests warn after eieio-compat.el was moved to obsolete/ Stefan Kangas
2022-01-03  4:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-03 16:48   ` Stefan Kangas
2022-01-14  8:59     ` Lars Ingebrigtsen [this message]

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=87lezipua3.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=52971@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefan@marxist.se \
    /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).