guile-email discussion
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 49115-done@debbugs.gnu.org, guile-email@systemreboot.net
Subject: Re: [PATCH 1/1] debbugs: Do not check for MIME encoded words in subject.
Date: Mon, 02 Jan 2023 20:34:52 +0100	[thread overview]
Message-ID: <87sfgs4tn8.fsf@elephly.net> (raw)
In-Reply-To: <20230102174312.9685-2-arunisaac@systemreboot.net>


Arun Isaac <arunisaac@systemreboot.net> writes:

> guile-email transparently handles MIME encoded words. We do not have
> to check for them.
>
> * mumi/debbugs.scm (bug-status): Do not check for MIME encoded words
> in subject.

Thank you, I applied it.

-- 
Ricardo


      reply	other threads:[~2023-01-02 19:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 22:53 Mumi inserts spurious underscore in bug title Ricardo Wurmus
2022-12-29 19:36 ` Arun Isaac
2023-01-01 12:15   ` Ricardo Wurmus
2023-01-02 17:43     ` [PATCH 0/1] Do not check for MIME encoded words Arun Isaac
2023-01-02 17:43     ` [PATCH 1/1] debbugs: Do not check for MIME encoded words in subject Arun Isaac
2023-01-02 19:34       ` Ricardo Wurmus [this message]

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=87sfgs4tn8.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=49115-done@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    --cc=guile-email@systemreboot.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox