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

Hi Ricardo,

I have an additional small improvement. guile-email transparently
handles MIME encoded words. We need not check for them. Patch follows.

Regards,
Arun

Arun Isaac (1):
  debbugs: Do not check for MIME encoded words in subject.

 mumi/debbugs.scm | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

-- 
2.38.1



  reply	other threads:[~2023-01-02 17:43 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     ` Arun Isaac [this message]
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

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=20230102174312.9685-1-arunisaac@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=49115-done@debbugs.gnu.org \
    --cc=guile-email@systemreboot.net \
    --cc=rekado@elephly.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