all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
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 21:19:16 +0300	[thread overview]
Message-ID: <83zh8n12aj.fsf@gnu.org> (raw)
In-Reply-To: <87imfbrsnk.fsf@tcd.ie> (contovob@tcd.ie)

> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Cc: juanjose.garcia.ripoll@csic.es,  40247@debbugs.gnu.org
> Date: Sun, 28 Jun 2020 18:45:19 +0100
> 
> > 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?

Could be, yes.

> 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.

That's okay, the bug doesn't sound too bad to me.

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

I don't really mind, those blocking attributes are advisory only.
This bug has been open for many moons and no one seemed to care too
much, so I don't see how it could be really blocking.





  reply	other threads:[~2020-06-28 18:19 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
2020-06-28 18:19       ` Eli Zaretskii [this message]
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=83zh8n12aj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=40247@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --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.