unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org
Subject: Re: Reply code with TEXT/PLAIN
Date: Mon, 26 Mar 2012 08:39:24 -0700	[thread overview]
Message-ID: <87zkb3jrrn.fsf@servo.finestructure.net> (raw)
In-Reply-To: <4F708A2D.90800@fifthhorseman.net>

[-- Attachment #1: Type: text/plain, Size: 658 bytes --]

On Mon, 26 Mar 2012 11:24:29 -0400, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
> On 03/26/2012 11:21 AM, Jameson Graef Rollins wrote:
> > Does it make sense for the cli to canonicalize the content types to
> > always be lower case?  Or should it continue to just pass the content
> > type exactly as it appears in the original message?  Given that
> > consumers should parse it case insensitively, it maybe doesn't matter,
> > but it might also be nice for us to be consistent.
> 
> i think "notmuch emits the content-type in the exact form contained in
> the underlying message" is a good flavor of consistency.

Works for me.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

      reply	other threads:[~2012-03-26 15:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 21:49 Reply code with TEXT/PLAIN Mark Walters
2012-03-25  0:19 ` Adam Wolfe Gordon
2012-03-25  0:43   ` [PATCH] emacs: content-type comparison should be case insensitive Mark Walters
2012-03-26 15:21     ` Jameson Graef Rollins
2012-03-26 19:40     ` Tomi Ollila
2012-03-31  0:30     ` David Bremner
2012-03-26 15:21   ` Reply code with TEXT/PLAIN Jameson Graef Rollins
2012-03-26 15:24     ` Daniel Kahn Gillmor
2012-03-26 15:39       ` Jameson Graef Rollins [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=87zkb3jrrn.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --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).