From: Austin Clements <amdragon@MIT.EDU>
To: notmuch@notmuchmail.org
Subject: [PATCH 0/3] Sync devel/schemata with code
Date: Wed, 7 Nov 2012 10:26:59 -0500 [thread overview]
Message-ID: <1352302022-21486-1-git-send-email-amdragon@mit.edu> (raw)
There were some recent changes to the JSON format without accompanying
schema documentation changes [1, 2]. Though, curiously, [1] was
documented in the schema long before it was implemented owing to a
historical twist (we *used* to have Bcc in the JSON output and then it
got lost [my fault, most likely]). Patches 2 and 3 try to increase
the visibility of the documentation; I'm open to better ways to do
this.
[1] id:7b1848a5828820912e3f7b960528b0dbc6a8b361.1347258748.git.mina86@mina86.com
[2] id:1351591967-17438-2-git-send-email-novalazy@gmail.com
next reply other threads:[~2012-11-07 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 15:26 Austin Clements [this message]
2012-11-07 15:27 ` [PATCH 1/3] devel: Add Reply-to to the schemata Austin Clements
2012-11-08 13:54 ` David Bremner
2012-11-07 15:27 ` [PATCH 2/3] show: More aggressively document the presence of devel/schemata Austin Clements
2012-11-07 15:27 ` [PATCH 3/3] devel: Document schemata in STYLE Austin Clements
2012-11-07 15:40 ` [PATCH 0/3] Sync devel/schemata with code 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=1352302022-21486-1-git-send-email-amdragon@mit.edu \
--to=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).