From: Junio C Hamano <gitster@pobox•com>
To: Jeff Hostetler <git@jeffhostetler•com>
Cc: git@vger•kernel.org, Jeff Hostetler <jeffhost@microsoft•com>
Subject: Re: [PATCH v8 0/9] status: V2 porcelain status
Date: Fri, 12 Aug 2016 15:08:34 -0700 [thread overview]
Message-ID: <xmqqfuq9vdwd.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1471016692-35828-1-git-send-email-git@jeffhostetler.com> (Jeff Hostetler's message of "Fri, 12 Aug 2016 11:44:43 -0400")
Jeff Hostetler <git@jeffhostetler•com> writes:
> This v8 patch series addresses the remaining feedback
> about the unit tests from the v6 and v7 series.
Thanks, will re-queue.
I didn't spot anything glaringly wrong in the last patch, and all
the ealier steps looked good in the previous round, so I think we
are getting there.
prev parent reply other threads:[~2016-08-12 22:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 15:44 [PATCH v8 0/9] status: V2 porcelain status Jeff Hostetler
2016-08-12 15:44 ` [PATCH v8 1/9] status: rename long-format print routines Jeff Hostetler
2016-08-12 15:44 ` [PATCH v8 2/9] status: cleanup API to wt_status_print Jeff Hostetler
2016-08-12 15:44 ` [PATCH v8 3/9] status: support --porcelain[=<version>] Jeff Hostetler
2016-08-12 15:44 ` [PATCH v8 4/9] status: collect per-file data for --porcelain=v2 Jeff Hostetler
2016-08-12 15:44 ` [PATCH v8 5/9] status: print per-file porcelain v2 status data Jeff Hostetler
2016-08-12 15:44 ` [PATCH v8 6/9] status: print branch info with --porcelain=v2 --branch Jeff Hostetler
2016-08-12 15:44 ` [PATCH v8 7/9] git-status.txt: describe --porcelain=v2 format Jeff Hostetler
2016-08-12 15:44 ` [PATCH v8 8/9] test-lib-functions.sh: Add lf_to_nul Jeff Hostetler
2016-08-12 15:44 ` [PATCH v8 9/9] status: unit tests for --porcelain=v2 Jeff Hostetler
2016-08-12 22:08 ` 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=xmqqfuq9vdwd.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@jeffhostetler$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jeffhost@microsoft$(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