unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonas Bernoulli <jonas@bernoul.li>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 54775@debbugs.gnu.org
Subject: bug#54775: debbugs uses functions not available in Emacs 25.1
Date: Fri, 08 Apr 2022 23:55:20 +0200	[thread overview]
Message-ID: <878rsfb5pz.fsf@bernoul.li> (raw)
In-Reply-To: <87mtgv34o5.fsf@gmx.de>

Michael Albinus <michael.albinus@gmx.de> writes:

> Jonas Bernoulli <jonas@bernoul.li> writes:
>
> Hi Jonas,
>
>> Hell no!  But there are people who want to use an ancient Emacsen (or
>> are being forced to do so by their employer) but also the very latest
>> Magit, so I am forced to occasionally check if things still work in 25.
>> When doing that I also have to recompile other packages and ran into
>> this issue.
>
> I see. I'll try to make debbugs compatible with Emacs 25, but it might
> take some days ...

You don't have to do that for me!  I don't use debbugs *while* checking
whether my packages are still backward compatible.  I just happen to
recompile every package that I have installed when I do that (except for
those that I have already added to my list of packages that are not
backward compatible).

I just described how I came across those warnings. I reported to inform
the maintainers that they should do *something* about it.  I didn't mean
to imply that in those situations I have an urgent need for debbugs to
be usable.  Depending on a more recent Emacs would be perfectly fine
with me.

     Jonas





  reply	other threads:[~2022-04-08 21:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 20:01 bug#54775: debbugs uses functions not available in Emacs 25.1 Jonas Bernoulli
2022-04-08 13:20 ` Lars Ingebrigtsen
2022-04-08 13:25   ` Michael Albinus
2022-04-08 16:19     ` Jonas Bernoulli
2022-04-08 16:45       ` Michael Albinus
2022-04-08 21:55         ` Jonas Bernoulli [this message]
2022-04-09  8:26           ` Michael Albinus

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=878rsfb5pz.fsf@bernoul.li \
    --to=jonas@bernoul.li \
    --cc=54775@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=michael.albinus@gmx.de \
    /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).