From: Mark Walters <markwalters1009@gmail.com>
To: Austin Clements <amdragon@MIT.EDU>, notmuch@notmuchmail.org
Subject: Re: [PATCH 0/7] Structed output versioning support
Date: Sun, 16 Dec 2012 07:42:50 +0000 [thread overview]
Message-ID: <87r4mqxx1h.fsf@qmul.ac.uk> (raw)
In-Reply-To: <1355627849-29099-1-git-send-email-amdragon@mit.edu>
LGTM +1
Best wishes
Mark
On Sun, 16 Dec 2012, Austin Clements <amdragon@MIT.EDU> wrote:
> This series obsoletes [0] and must be applied on top of the Emacs CLI
> error handling series [1]. This is much simpler than the original
> series because it no longer includes the Emacs CLI error handling.
> This also switches to a CLI-wide minimum version instead of a
> per-command version, prints a warning if an old but still supported
> version is requested to ease client maintenance, and renames
> --use-schema to --format-version (which parallels --format better and
> simplifies error text).
>
> [0] id:1354416002-3557-1-git-send-email-amdragon@mit.edu
> [1] id:1355601860-30121-1-git-send-email-amdragon@mit.edu
prev parent reply other threads:[~2012-12-16 7:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 3:17 [PATCH 0/7] Structed output versioning support Austin Clements
2012-12-16 3:17 ` [PATCH 1/7] cli: Framework for structured output versioning Austin Clements
2012-12-16 21:39 ` David Bremner
2012-12-16 3:17 ` [PATCH 2/7] search: Support --format-version Austin Clements
2012-12-16 3:17 ` [PATCH 3/7] show: " Austin Clements
2012-12-16 3:17 ` [PATCH 4/7] reply: " Austin Clements
2012-12-16 3:17 ` [PATCH 5/7] test: Sanity tests for the --format-version argument Austin Clements
2012-12-16 3:17 ` [PATCH 6/7] emacs: Special handling for version mismatch errors Austin Clements
2012-12-16 3:17 ` [PATCH 7/7] emacs: Use --format-version for search, show, and reply Austin Clements
2012-12-16 4:03 ` [PATCH 0/7] Structed output versioning support Tomi Ollila
2012-12-16 7:42 ` Mark Walters [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=87r4mqxx1h.fsf@qmul.ac.uk \
--to=markwalters1009@gmail.com \
--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).