From: Jonathan Tan <jonathantanmy@google.com>
To: git@vger.kernel.org
Cc: Jonathan Tan <jonathantanmy@google.com>,
bmwill@google.com, gitster@pobox.com, larsxschneider@gmail.com
Subject: [PATCH for NEXT v3 0/2] sub-process: refactor handshake to common function
Date: Wed, 26 Jul 2017 11:17:27 -0700 [thread overview]
Message-ID: <cover.1501092795.git.jonathantanmy@google.com> (raw)
In-Reply-To: <20170724213810.29831-1-jonathantanmy@google.com>
Thanks for all your comments.
This is now built off "next" to include Lars's changes.
About whether this is too restrictive (for example, as Junio mentions,
this will not allow future capabilities of the form "key=???"), I think
that this can be upgraded later if necessary. For now, both the filter
code and the ODB (and ODB-like) proposals on the mailing list do not
require such a thing, so I have not included that functionality.
Changes from v2:
- now rebased onto next, to pick up Lars's changes
- split up into more functions
- welcome prefix does not include final dash
- no more gotos in expected cases (or at all)
Jonathan Tan (2):
Documentation: migrate sub-process docs to header
sub-process: refactor handshake to common function
Documentation/technical/api-sub-process.txt | 59 ----------------
convert.c | 75 ++------------------
pkt-line.c | 19 -----
pkt-line.h | 2 -
sub-process.c | 103 ++++++++++++++++++++++++++++
sub-process.h | 51 +++++++++++++-
t/t0021-conversion.sh | 2 +-
7 files changed, 160 insertions(+), 151 deletions(-)
delete mode 100644 Documentation/technical/api-sub-process.txt
--
2.14.0.rc0.400.g1c36432dff-goog
next prev parent reply other threads:[~2017-07-26 18:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 21:38 [PATCH] sub-process: refactor handshake to common function Jonathan Tan
2017-07-24 22:21 ` Jonathan Nieder
2017-07-25 14:38 ` Ben Peart
2017-07-25 17:53 ` Jonathan Tan
2017-07-25 18:29 ` [PATCH v2 0/2] " Jonathan Tan
2017-07-25 18:29 ` [PATCH v2 1/2] Documentation: migrate sub-process docs to header Jonathan Tan
2017-07-25 20:18 ` Brandon Williams
2017-07-25 18:29 ` [PATCH v2 2/2] sub-process: refactor handshake to common function Jonathan Tan
2017-07-25 20:28 ` Brandon Williams
2017-07-25 22:25 ` Junio C Hamano
2017-07-26 16:52 ` [PATCH] " Lars Schneider
2017-07-26 18:14 ` Junio C Hamano
2017-07-26 18:17 ` Jonathan Tan [this message]
2017-07-26 19:48 ` [PATCH for NEXT v3 0/2] " Junio C Hamano
2017-07-29 16:26 ` Junio C Hamano
2017-07-26 18:17 ` [PATCH for NEXT v3 1/2] Documentation: migrate sub-process docs to header Jonathan Tan
2017-07-26 18:17 ` [PATCH for NEXT v3 2/2] sub-process: refactor handshake to common function Jonathan Tan
2017-08-06 19:58 ` Lars Schneider
2017-08-07 17:21 ` Jonathan Tan
2017-08-07 17:51 ` Lars Schneider
2017-08-07 18:17 ` Jonathan Tan
2017-08-07 18:29 ` Ben Peart
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1501092795.git.jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
/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.
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 NNTP newsgroup(s).