Alejandro Colomar

v1e changes: - Reviewed-by @nabijaczleweli (I transformed your approval on GH to a tag in the commit; please express yourself if you disagree) Thanks! ``` $ git range-diff devel/security gh/cryptoweed...

> I'm not sure the combinations of weed and crypt_protected_headers_weed make sense: with this approach, it's not possible to weed protected headers only and leave regular headers alone (not saying...

v1f changes: - Cc @gahr ``` $ git range-diff devel/security gh/cryptoweed cryptoweed 1: 66625aa49 ! 1: 1e23dbea3 $crypt_protected_headers_weed: Add variable @@ Commit message Link: Cc: Richard Russon Reviewed-by: наб +...

> > I don't see why one would want to weed crypto headers but not weed the normal ones. > > At most, one could want to hide all crypto...

> So sorry, I've been meaning to write `crypt_protected_headers_weed` all the time. > > How would you explain `weed=no; crypt_protected_headers_weed=yes` > So sorry, I've been meaning to write `crypt_protected_headers_weed` all...

> I have a feeling that, then, weed should control everything. But it's not a strong feeling. Whatever works for you, honestly. There's prior art in something similar: ``` copy_decode_weed...

> I have a feeling that, then, weed should control everything. But it's not a strong feeling. Whatever works for you, honestly. I think I disagree, because most people want...

v1g (by @flatcap ) changes: - Rebase ``` $ git range-diff devel/security..cryptoweed neomutt/devel/security..gh/cryptoweed 1: 1e23dbea3 = 1: a59ee02a5 $crypt_protected_headers_weed: Add variable ```

v1h changes: - Rebase ``` $ git range-diff main..gh/cryptoweed devel/security..cryptoweed 1: a59ee02a5 = 1: 41e0f1215 $crypt_protected_headers_weed: Add variable ```

Hmmmm. Could be. Feel free to close the issue as WONTFIX.