From: Jules Aguillon <juloo.dsi@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: [PATCH] Vim: Fix a deprecated call to the 'mail' gem
Date: Mon, 3 May 2021 11:31:53 +0200 [thread overview]
Message-ID: <CAMCYqg4AVjN=vn=bHC-WrU22fA40cvK+0GJYaaWW33H32MXBAw@mail.gmail.com> (raw)
In-Reply-To: <CAMP44s0pgjEmDXfQ16YHkkNeBr2KwkdE9YcZU3q8PhEANZBGSw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 861 bytes --]
Hi !
This is indeed fixed on master. My patch has the advantage of removing the
extraneous "to string" and "parsing" steps but that's not a big deal.
Thanks!
On Sun, May 2, 2021 at 11:51 PM Felipe Contreras <felipe.contreras@gmail.com>
wrote:
> On Sun, May 2, 2021 at 5:43 AM David Bremner <david@tethera.net> wrote:
> >
> > Jules Aguillon <juloo.dsi@gmail.com> writes:
> >
> > > The Field.new function from the 'mail' gem changed recently (since
> > > 2.7.0, Nov 2017) and now prints a message on stdout:
> > >
> > >> Passing an unparsed header field to Mail::Field.new is deprecated and
> will be removed in Mail 2.8.0. Use Mail::Field.parse instead.
> >
> > I believe this problem was fixed in a different way by Felipe's patch
> > applied as 8af4cd16
>
> Indeed, but Jules' patch may be a better solution, I will investigate.
>
> --
> Felipe Contreras
>
[-- Attachment #1.2: Type: text/html, Size: 1728 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2021-05-03 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 22:20 [PATCH] Vim: Fix a deprecated call to the 'mail' gem Jules Aguillon
2021-05-02 10:43 ` David Bremner
2021-05-02 21:51 ` Felipe Contreras
2021-05-03 9:31 ` Jules Aguillon [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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMCYqg4AVjN=vn=bHC-WrU22fA40cvK+0GJYaaWW33H32MXBAw@mail.gmail.com' \
--to=juloo.dsi@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=notmuch@notmuchmail.org \
/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 public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).