public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Ben Peart <peartben@gmail•com>
Cc: git@vger•kernel.org, benpeart@microsoft•com,
	christian.couder@gmail•com, larsxschneider@gmail•com
Subject: Re: [PATCH v4 0/8] refactor the filter process code into a reusable module
Date: Thu, 30 Mar 2017 13:11:53 -0700	[thread overview]
Message-ID: <xmqqpogy34om.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170330155417.8928-1-benpeart@microsoft.com> (Ben Peart's message of "Thu, 30 Mar 2017 11:54:08 -0400")

Now 1 & 2 are as equally pleasant to read as others ;-).

Let's wait for a few days and then merge to 'next'.  I didn't see
anything questionable.

Thanks.

      parent reply	other threads:[~2017-03-30 20:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 15:54 [PATCH v4 0/8] refactor the filter process code into a reusable module Ben Peart
2017-03-30 15:54 ` [PATCH v4 1/8] pkt-line: add packet_read_line_gently() Ben Peart
2017-03-30 15:54 ` [PATCH v4 2/8] convert: move packet_write_list() into pkt-line as packet_writel() Ben Peart
2017-03-30 15:54 ` Ben Peart
2017-03-30 15:54 ` [PATCH v4 3/8] convert: Split start_multi_file_filter into two separate functions Ben Peart
2017-03-30 15:54 ` [PATCH v4 4/8] convert: Separate generic structures and variables from the filter specific ones Ben Peart
2017-03-30 15:54 ` [PATCH v4 5/8] convert: Update generic functions to only use generic data structures Ben Peart
2017-03-30 15:54 ` [PATCH v4 6/8] convert: rename reusable sub-process functions Ben Peart
2017-03-30 15:54 ` [PATCH v4 7/8] sub-process: move sub-process functions into separate files Ben Peart
2017-03-30 15:54 ` [PATCH v4 8/8] convert: Update subprocess_read_status to not die on EOF Ben Peart
2017-03-30 20:11 ` Junio C Hamano [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqpogy34om.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=benpeart@microsoft$(echo .)com \
    --cc=christian.couder@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=larsxschneider@gmail$(echo .)com \
    --cc=peartben@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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