unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Stefano Zacchiroli <zack@upsilon.cc>
To: notmuch@notmuchmail.org
Cc: zack@upsilon.cc
Subject: notmuch-mutt: support for messages that lack Message-ID headers (v3)
Date: Sun, 15 Feb 2015 13:39:05 +0100	[thread overview]
Message-ID: <1424003948-17642-1-git-send-email-zack@upsilon.cc> (raw)
In-Reply-To: <m2twyvyx41.fsf@guru.guru-group.fi>

Take #3 on adding support for messages that lack Message-ID headers to
notmuch-mutt. For context see:
- http://notmuchmail.org/pipermail/notmuch/2015/thread.html#20171
- http://notmuchmail.org/pipermail/notmuch/2015/thread.html#20079

I've rewritten the patch taking into account the suggestions by Tomi
Ollila, who suggested a much cleaner approach for processing headers
and possibly fallback to synthetic Message-IDs (thanks Tomi!).

I'll be happy to hear further comments on this patch series.
If there are none, please merge it into master.

Cheers.

  reply	other threads:[~2015-02-15 12:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09  9:41 notmuch-mutt: support for messages that lack Message-ID (v2) Stefano Zacchiroli
2015-02-09  9:41 ` [PATCH 1/2] notmuch-mutt README: use metacpn.org/* as deps homepages Stefano Zacchiroli
2015-02-09  9:41 ` [PATCH 2/2] notmuch-mutt: support for messages that lack Message-ID headers Stefano Zacchiroli
2015-02-09 14:31   ` Tomi Ollila
2015-02-15 12:39     ` Stefano Zacchiroli [this message]
2015-02-15 12:39       ` [PATCH 1/3] notmuch-mutt: bump copyright year Stefano Zacchiroli
2015-02-15 12:39       ` [PATCH 2/3] notmuch-mutt README: use metacpn.org/* as deps homepages Stefano Zacchiroli
2015-02-15 12:39       ` [PATCH 3/3] notmuch-mutt: support for messages that lack Message-ID headers Stefano Zacchiroli
2015-02-15 16:46       ` notmuch-mutt: support for messages that lack Message-ID headers (v3) Tomi Ollila
2015-02-16 13:00       ` David Bremner

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=1424003948-17642-1-git-send-email-zack@upsilon.cc \
    --to=zack@upsilon.cc \
    --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).