From a91871ec6b607d73502ee447af8ccc9e4bfe5098 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Sun, 10 May 2020 09:42:02 +0000 Subject: emlcontentfoo: drop the {discrete} and {composite} fields We don't have to worry about compatibility with old installations of Email::MIME::ContentType any longer, so save some space. --- lib/PublicInbox/EmlContentFoo.pm | 10 ---------- 1 file changed, 10 deletions(-) (limited to 'lib/PublicInbox/EmlContentFoo.pm') diff --git a/lib/PublicInbox/EmlContentFoo.pm b/lib/PublicInbox/EmlContentFoo.pm index e6005d29..c163eaf5 100644 --- a/lib/PublicInbox/EmlContentFoo.pm +++ b/lib/PublicInbox/EmlContentFoo.pm @@ -102,11 +102,6 @@ sub parse_content_type { type => $type, subtype => $subtype, attributes => $attributes, - - # This is dumb. Really really dumb. For backcompat. -- rjbs, - # 2013-08-10 - discrete => $type, - composite => $subtype, }; } @@ -301,11 +296,6 @@ This routine parses email content type headers according to section 5.1 of RFC a hash as above, with entries for the C, the C, and a hash of C. -For backward compatibility with a really unfortunate misunderstanding of RFC -2045 by the early implementors of this module, C and C are -also present in the returned hashref, with the values of C and C -respectively. - =func parse_content_disposition This routine is exported by default. -- cgit v1.2.3-24-ge0c7