From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 36403@debbugs.gnu.org
Subject: bug#36403: 27.0.50; Trivial image.c bugs
Date: Fri, 28 Jun 2019 22:52:50 +0300 [thread overview]
Message-ID: <83h889h4h9.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBc3gqbA9im1oUZ=N-y-M30PJwkzWkhvDmRRrpaJnF2tuw@mail.gmail.com> (message from Pip Cet on Fri, 28 Jun 2019 15:05:30 +0000)
> From: Pip Cet <pipcet@gmail.com>
> Date: Fri, 28 Jun 2019 15:05:30 +0000
> Cc: 36403@debbugs.gnu.org
>
> > Thanks, but please also add tests which verify that these problems no
> > longer happen after the fix.
>
> Thanks for reminding me of that! I looked into that, and it seems
> there are no image tests so far.
There are some in test/manual. they are there because they need to be
run interactively.
> Attached patch has tests and fixes.
Thanks. Let's wait for a few days to let others comment.
next prev parent reply other threads:[~2019-06-28 19:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 16:28 bug#36403: 27.0.50; Trivial image.c bugs Pip Cet
2019-06-27 17:40 ` Eli Zaretskii
2019-06-28 15:05 ` Pip Cet
2019-06-28 19:52 ` Eli Zaretskii [this message]
2019-07-22 2:55 ` Pip Cet
2019-07-26 6:56 ` Eli Zaretskii
2019-07-28 14:50 ` Pip Cet
2019-09-24 16:26 ` Lars Ingebrigtsen
2020-08-03 7:47 ` Lars Ingebrigtsen
2020-08-18 16:28 ` Lars Ingebrigtsen
2020-08-20 23:03 ` Alan Third
2020-08-20 23:13 ` Lars Ingebrigtsen
2020-08-20 23:17 ` Lars Ingebrigtsen
2020-08-20 23:32 ` Lars Ingebrigtsen
2020-08-21 9:26 ` Pip Cet
2020-08-21 11:26 ` Lars Ingebrigtsen
2022-10-04 13:52 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 14:06 ` Lars Ingebrigtsen
2022-10-04 18:05 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 22:14 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h889h4h9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36403@debbugs.gnu.org \
--cc=pipcet@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.