From: David Bremner <david@tethera.net>
To: "W. Trevor King" <wking@tremily.us>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] nmbug: Allow Unicode tags and IDs in Python 2
Date: Tue, 16 Feb 2016 14:37:14 -0400 [thread overview]
Message-ID: <87wpq4v6w5.fsf@tesseract.cs.unb.ca> (raw)
In-Reply-To: <20160216175641.GN4265@odin.tremily.us>
"W. Trevor King" <wking@tremily.us> writes:
>
>> At first I thought there might be problems with non-utf8 message-ids,
>> but that turns out not to be the case [1]. It seems like it would take
>> a fairly heroic effort to get non-UTF8 tags into the database (perhaps
>> by calling the library interface with bad strings?) so we can probably
>> ignore this case. It might be good to document the limitation though,
>> since AFAIK, dump and restore can roundtrip any old crap.
>
> How about in a NEWS entry in v2 of this series, and then echoing that
> NEWS entry in the notmuch-dtags (or whatever) man page once I work up
> that series?
Sure, sounds fine
d
prev parent reply other threads:[~2016-02-16 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 5:30 [PATCH] nmbug: Allow Unicode tags and IDs in Python 2 W. Trevor King
2016-02-16 13:04 ` David Bremner
2016-02-16 17:56 ` W. Trevor King
2016-02-16 18:37 ` David Bremner [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=87wpq4v6w5.fsf@tesseract.cs.unb.ca \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=wking@tremily.us \
/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).