From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: matsievskiysv@gmail.com, 44655@debbugs.gnu.org
Subject: bug#44655: 28.0.50; Oversized SVG margin
Date: Sun, 15 Nov 2020 17:33:39 +0000 [thread overview]
Message-ID: <20201115173339.GB1370@breton.holly.idiocy.org> (raw)
In-Reply-To: <83h7pqttlz.fsf@gnu.org>
On Sun, Nov 15, 2020 at 07:31:04PM +0200, Eli Zaretskii wrote:
> > Date: Sun, 15 Nov 2020 17:25:35 +0000
> > From: Alan Third <alan@idiocy.org>
> > Cc: 44655@debbugs.gnu.org
> >
> > All I can think of to do is ignore the deprecation of
> > svg_handle_get_dimensions and continue using it. The release notes for
> > librsvg 2.46 state it's deprecated but still available.
> >
> > Patch attached. Are we happy to continue using deprecated functions?
>
> Could it cause compilation failure if strict compiler switches are
> used?
I don't believe so. They say they're still available. What switches
should I try?
--
Alan Third
next prev parent reply other threads:[~2020-11-15 17:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 8:59 bug#44655: 28.0.50; Oversized SVG margin Matsievskiy S.V.
2020-11-15 17:25 ` Alan Third
2020-11-15 17:31 ` Eli Zaretskii
2020-11-15 17:33 ` Alan Third [this message]
2020-11-15 17:47 ` Eli Zaretskii
2020-11-15 17:56 ` Alan Third
2020-11-16 22:34 ` Lars Ingebrigtsen
2020-11-15 17:39 ` Matsievskiy S.V.
2020-11-15 17:52 ` Alan Third
2020-11-18 21:40 ` Matsievskiy S.V.
2020-11-18 23:08 ` Alan Third
2020-11-20 0:18 ` Andy Moreton
2020-11-20 15:02 ` Eli Zaretskii
2020-11-20 15:39 ` Andy Moreton
2021-11-05 19:28 ` Paul Eggert
2021-11-06 12:55 ` Alan Third
2021-12-03 18:45 ` Paul Eggert
2021-12-04 10:46 ` Alan Third
2021-12-04 11:00 ` Arash Esbati
2021-12-04 11:43 ` Eli Zaretskii
2021-12-04 12:05 ` Arash Esbati
2021-12-04 16:07 ` 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=20201115173339.GB1370@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=44655@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=matsievskiysv@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).