unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 27952@debbugs.gnu.org
Subject: bug#27952: 26.0.50; Combine archive-int-to-mode and tar-grind-file-mode
Date: Thu, 14 May 2020 20:23:34 +0300	[thread overview]
Message-ID: <83y2pu4ei1.fsf@gnu.org> (raw)
In-Reply-To: <87d076piop.fsf@calancha-pc.dy.bbexcite.jp> (message from Tino Calancha on Thu, 14 May 2020 18:47:34 +0200)

> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Thu, 14 May 2020 18:47:34 +0200
> 
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
> 
> > LGTM.
> 
> Fixed in master branch as commit
> 'Combine archive-int-to-mode and tar-grind-file-mode'
> (3a284e578625e617fdc6085ae11da2b4e41bb59b)

The fix triggers compilation warnings:

  In archive--summarize-descs:
  arc-mode.el:1509:45: Warning: `archive-int-to-mode' is an obsolete function
      (as of 28.1); use `file-modes-number-to-symbolic' instead.
  arc-mode.el:1574:70: Warning: `archive-int-to-mode' is an obsolete function
      (as of 28.1); use `file-modes-number-to-symbolic' instead.

Would it be possible to eliminate these warnings, please?

Thanks.





  reply	other threads:[~2020-05-14 17:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 12:32 bug#27952: 26.0.50; Combine archive-int-to-mode and tar-grind-file-mode Tino Calancha
2017-08-16 11:43 ` Tino Calancha
2017-08-16 12:00   ` npostavs
2017-08-16 13:13     ` Tino Calancha
2017-08-16 12:08   ` Andreas Schwab
2017-08-16 13:10     ` Tino Calancha
2019-06-24 20:35 ` Lars Ingebrigtsen
2019-06-24 20:42   ` Tino Calancha
2019-11-11  3:07     ` Stefan Kangas
2019-11-13 16:58       ` Tino Calancha
2020-05-04 11:55         ` Stefan Kangas
2020-05-08 19:53           ` Tino Calancha
2020-05-08 20:06             ` Stefan Monnier
2020-05-08 20:20               ` Tino Calancha
2020-05-14 16:47               ` Tino Calancha
2020-05-14 17:23                 ` Eli Zaretskii [this message]
2020-05-14 20:08                   ` Tino Calancha
2020-05-15  6:22                     ` 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=83y2pu4ei1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27952@debbugs.gnu.org \
    --cc=tino.calancha@gmail.com \
    /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).