From: Michal Nazarewicz <mpn@google.com>
To: Tomi Ollila <tomi.ollila@iki.fi>, David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] Add NEWS information about Bcc header in JSON output
Date: Wed, 07 Nov 2012 15:03:22 +0100 [thread overview]
Message-ID: <xa1ta9uta4t1.fsf@mina86.com> (raw)
In-Reply-To: <m2d2zp7edt.fsf@guru.guru-group.fi>
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
On Wed, Nov 07 2012, Tomi Ollila wrote:
> Also, I don't know whether markdown allows the text in backticks (``)
> be split into 2 lines -- at the end it's me who is going to do final
> corrections there ;) (luckily that probably changes when more text
> is added to the sentences.
OK, so can I forget about this and assume you're take care of it? :P
Thanks!
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +----<email/xmpp: mpn@google.com>--------------ooO--(_)--Ooo--
[-- Attachment #2.1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2.2: Type: application/pgp-signature, Size: 835 bytes --]
prev parent reply other threads:[~2012-11-07 14:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 21:40 [PATCH] notmuch-show: include Bcc header in json output Michal Nazarewicz
2012-09-06 14:31 ` Michal Sojka
2012-09-06 15:16 ` Michal Nazarewicz
2012-09-07 11:52 ` Michal Sojka
2012-09-08 11:29 ` Tomi Ollila
2012-09-10 6:35 ` [PATCHv3] " Michal Nazarewicz
2012-09-10 8:52 ` Tomi Ollila
2012-09-10 9:13 ` Michal Nazarewicz
2012-09-10 9:30 ` Tomi Ollila
2012-09-10 9:41 ` Michal Nazarewicz
2012-10-20 15:58 ` Ethan Glasser-Camp
2012-10-22 23:09 ` David Bremner
2012-10-29 16:08 ` [PATCH] Add NEWS information about Bcc header in JSON output Michal Nazarewicz
2012-10-31 21:40 ` David Bremner
2012-11-01 13:51 ` Michal Nazarewicz
2012-11-07 12:09 ` David Bremner
2012-11-07 13:04 ` Tomi Ollila
2012-11-07 14:03 ` Michal Nazarewicz [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=xa1ta9uta4t1.fsf@mina86.com \
--to=mpn@google.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).