all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Eli Zaretskii <eliz@gnu.org>
Cc: juanjose.garcia.ripoll@csic.es, 40247@debbugs.gnu.org
Subject: bug#40247: 27.0.90; mailcap-mime-data erased when parsing mime parts
Date: Sun, 28 Jun 2020 18:45:19 +0100	[thread overview]
Message-ID: <87imfbrsnk.fsf@tcd.ie> (raw)
In-Reply-To: <834kqv2jlb.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 28 Jun 2020 20:20:16 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: "Basil L. Contovounesios" <contovob@tcd.ie>
>> Date: Sun, 28 Jun 2020 18:11:00 +0100
>> Cc: 40247@debbugs.gnu.org
>> 
>> I think this is a symptom of the fix for bug#36771, and therefore
>> affects systems with mailcap files as well.
>> 
>> Since it affects me too and block Emacs 27.1, I plan to look into it in
>> about a week's time if no-one beats me to it.
>
> That might be too late: we hope to have the first RC this week or the
> next.

That just means the bug won't be fixed until 27.2 or 28.1, right?

Unfortunately my hands are completely tied until Thursday (I shouldn't
even be writing this email!), and either way I think the fix will
involve non-trivial code changes.

Should bug#39200 therefore be marked as no longer blocked by this?

Thanks,

-- 
Basil





  reply	other threads:[~2020-06-28 17:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 22:53 bug#40247: 27.0.90; mailcap-mime-data erased when parsing mime parts Juan José García Ripoll
2020-06-28 17:11 ` Basil L. Contovounesios
2020-06-28 17:20   ` Eli Zaretskii
2020-06-28 17:45     ` Basil L. Contovounesios [this message]
2020-06-28 18:19       ` Eli Zaretskii
2020-08-02  6:20 ` Lars Ingebrigtsen
2020-08-02  7:05   ` Lars Ingebrigtsen
2020-08-03 14:41     ` Juan José García-Ripoll
2020-08-04  8:35       ` Lars Ingebrigtsen

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=87imfbrsnk.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=40247@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=juanjose.garcia.ripoll@csic.es \
    /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.