From: William Casarin <jb55@jb55.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: v3 of legacy-display cleanup
Date: Mon, 24 Jun 2019 20:06:24 -0700 [thread overview]
Message-ID: <87zhm6l5xr.fsf@jb55.com> (raw)
In-Reply-To: <20190625014107.12452-1-dkg@fifthhorseman.net>
Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
> This is the third revision of the series that cleans up legacy-display
> protected headers parts so that notmuch users only have to look at one
> subject line.
>
> version 2 can be found at id:20190531075907.17035-1-dkg@fifthhorseman.net
> version 1 can be found at id:20190531042825.27774-1-dkg@fifthhorseman.net
>
> ----------
> Now that notmuch can handle and interpret protected subject lines, it
> should also avoid forcing the user to look at "legacy display" parts
> that some MUAs (notably enigmail) copies of the protected headers that
> are intended to be rendered only by legacy clients -- clients capable
> of decryption but which don't understand how to handle protected
> headers.
> ----------
>
> The main differences from version 2 are:
>
> * i've directly included the two-patch "repair" series (originally
> found at id:20190531074027.16337-1-dkg@fifthhorseman.net), and
>
> * i've rebased against the uncrustified master, as well as applying
> the uncrustify rules to my changes here.
>
> If we can get this merged, i'll send a subsequent revision of the
> series that repairs "mixed-up MIME" mangled messages.
>
> I would appreciate any feedback!
Looks good to me, didn't get a chance to test it out yet. Thanks for
working on this!
Cheers,
Will
--
https://jb55.com
prev parent reply other threads:[~2019-06-25 3:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 1:41 v3 of legacy-display cleanup Daniel Kahn Gillmor
2019-06-25 1:41 ` [PATCH 1/7] mime-node: split out _mime_node_set_up_part Daniel Kahn Gillmor
2019-06-25 2:43 ` William Casarin
2019-06-25 17:59 ` Daniel Kahn Gillmor
2019-06-25 1:41 ` [PATCH 2/7] repair: set up codebase for repair functionality Daniel Kahn Gillmor
2019-06-25 1:41 ` [PATCH 3/7] test: avoid showing legacy-display parts Daniel Kahn Gillmor
2019-06-25 1:41 ` [PATCH 4/7] util/crypto: _n_m_crypto_potential_payload returns whether part is the payload Daniel Kahn Gillmor
2019-07-31 11:57 ` David Bremner
2019-08-01 3:15 ` Daniel Kahn Gillmor
2019-08-01 3:29 ` Daniel Kahn Gillmor
2019-08-01 11:32 ` David Bremner
2019-08-01 14:10 ` Daniel Kahn Gillmor
2019-08-01 11:33 ` David Bremner
2019-06-25 1:41 ` [PATCH 5/7] util/repair: add _notmuch_repair_crypto_payload_skip_legacy_display Daniel Kahn Gillmor
2019-06-25 3:02 ` William Casarin
2019-06-25 18:10 ` Daniel Kahn Gillmor
2019-08-03 15:15 ` David Bremner
2019-08-06 13:08 ` Daniel Kahn Gillmor
2019-06-25 1:41 ` [PATCH 6/7] cli/{show,reply}: skip over legacy-display parts Daniel Kahn Gillmor
2019-06-25 1:41 ` [PATCH 7/7] index: avoid indexing " Daniel Kahn Gillmor
2019-06-25 3:06 ` William Casarin [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=87zhm6l5xr.fsf@jb55.com \
--to=jb55@jb55.com \
--cc=dkg@fifthhorseman.net \
--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).