unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Austin Clements <amdragon@MIT.EDU>, notmuch@notmuchmail.org
Subject: Re: [PATCH v2 1/8] Document the JSON schemata used by show and search
Date: Mon, 27 Feb 2012 22:47:58 -0400	[thread overview]
Message-ID: <87ty2bbrmp.fsf@zancas.localnet> (raw)
In-Reply-To: <1329697590-7404-2-git-send-email-amdragon@mit.edu>

On Sun, 19 Feb 2012 19:26:23 -0500, Austin Clements <amdragon@MIT.EDU> wrote:
> ---
>  devel/schemata   |  138 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  notmuch-search.c |    3 +
>  notmuch-show.c   |    2 +

Pushed just the first in the series.

d

  reply	other threads:[~2012-02-28  2:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 17:33 [PATCH 0/8] Rewrite JSON show format Austin Clements
2012-02-14 17:33 ` [PATCH 1/8] Document the JSON schemata used by show and search Austin Clements
2012-02-14 17:33 ` [PATCH 2/8] show: Convert JSON format to the new self-recursive style Austin Clements
2012-02-14 17:33 ` [PATCH 3/8] show: Use consistent header ordering in the JSON format Austin Clements
2012-02-14 17:33 ` [PATCH 4/8] show: Unify JSON header output for messages and message parts Austin Clements
2012-02-14 17:33 ` [PATCH 5/8] show: Simplify talloc use in format_headers_json Austin Clements
2012-02-14 17:33 ` [PATCH 6/8] show: Make JSON helper functions print complete objects Austin Clements
2012-02-14 17:33 ` [PATCH 7/8] show: Make format_part_sigstatus_json's API consistent between GMIME 2.4 and 2.6 Austin Clements
2012-02-14 17:33 ` [PATCH 8/8] show: Further general simplifications of the JSON formatter Austin Clements
2012-02-15  5:45 ` [PATCH 0/8] Rewrite JSON show format Adam Wolfe Gordon
2012-02-15 15:00 ` Tomi Ollila
2012-02-15 15:20   ` Adam Wolfe Gordon
2012-02-15 18:15   ` Austin Clements
2012-02-20  0:26 ` [PATCH v2 " Austin Clements
2012-02-20  0:26   ` [PATCH v2 1/8] Document the JSON schemata used by show and search Austin Clements
2012-02-28  2:47     ` David Bremner [this message]
2012-02-20  0:26   ` [PATCH v2 2/8] show: Convert JSON format to the new self-recursive style Austin Clements
2012-03-01 12:35     ` David Bremner
2012-02-20  0:26   ` [PATCH v2 3/8] show: Use consistent header ordering in the JSON format Austin Clements
2012-02-20  0:26   ` [PATCH v2 4/8] show: Unify JSON header output for messages and message parts Austin Clements
2012-02-20  0:26   ` [PATCH v2 5/8] show: Simplify talloc use in format_headers_json Austin Clements
2012-02-20  0:26   ` [PATCH v2 6/8] show: Make JSON helper functions print complete objects Austin Clements
2012-02-20  0:26   ` [PATCH v2 7/8] show: Make format_part_sigstatus_json's API consistent between GMIME 2.4 and 2.6 Austin Clements
2012-02-20  0:26   ` [PATCH v2 8/8] show: Further general simplifications of the JSON formatter Austin Clements
2012-02-20 10:17   ` [PATCH v2 0/8] Rewrite JSON show format Tomi Ollila

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=87ty2bbrmp.fsf@zancas.localnet \
    --to=david@tethera.net \
    --cc=amdragon@MIT.EDU \
    --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).