From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Antoine Beaupré" <anarcat@orangeseeds.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH] Add --message-headers flag to notmuch-show
Date: Tue, 12 Nov 2019 12:19:01 -0500 [thread overview]
Message-ID: <8736etqagq.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87lfsl6qop.fsf@curie.anarc.at>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
On Tue 2019-11-12 10:48:54 -0500, Antoine Beaupré wrote:
> They need User-Agent:, I want Archive-At:, they will want
> X-Mailer... when is it going to stop?
It's going to stop when users are satisfied. :) I highly doubt that we
will reach all possible headers.
> I would rather have configurability here than and endless stream of
> patches to grow a possibly boundless list...
Configurability is at least as expensive to maintain as a (not actually
endless) short stream of patches, but i understand different people have
different tradeoffs they're willing to make.
Can you suggest which kind of configurability you would prefer: complete
override, or differential modification? And if so, why do you prefer it
over the other choice? or should there be both?
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-11-12 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 12:49 [PATCH] Add --message-headers flag to notmuch-show Johan Parin
2019-11-10 12:56 ` Johan Parin
2019-11-11 15:26 ` Daniel Kahn Gillmor
2019-11-11 15:39 ` Daniel Kahn Gillmor
2019-11-12 15:48 ` Antoine Beaupré
2019-11-12 17:19 ` Daniel Kahn Gillmor [this message]
2019-11-12 17:27 ` Antoine Beaupré
2019-11-12 19:24 ` Johan Parin
2019-11-12 22:19 ` Daniel Kahn Gillmor
2019-11-12 23:30 ` Tomi Ollila
2019-11-14 0:23 ` Daniel Kahn Gillmor
2019-11-14 20:44 ` Tomi Ollila
2019-11-15 16:59 ` Daniel Kahn Gillmor
2019-11-13 9:37 ` David Edmondson
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=8736etqagq.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=anarcat@orangeseeds.org \
--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).