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 v6 0/9] status: V2 porcelain status
Date: Thu, 11 Aug 2016 11:59:57 -0700 [thread overview]
Message-ID: <xmqqinv7168i.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1470926762-25394-1-git-send-email-git@jeffhostetler.com> (Jeff Hostetler's message of "Thu, 11 Aug 2016 10:45:53 -0400")
Jeff Hostetler <git@jeffhostetler.com> writes:
> From: Jeff Hostetler <jeffhost@microsoft.com>
>
> This patch series adds porcelain V2 format to status.
> This provides detailed information about file changes
> and about the current branch.
Everything up to 8/9 I didn't have anything to comment on; I didn't
see anything that smelled fishy, or anything I'd want to improve.
I did have a few minor nits in 9/9, though.
Thanks.
prev parent reply other threads:[~2016-08-11 19:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 14:45 [PATCH v6 0/9] status: V2 porcelain status Jeff Hostetler
2016-08-11 14:45 ` [PATCH v6 1/9] status: rename long-format print routines Jeff Hostetler
2016-08-11 14:45 ` [PATCH v6 2/9] status: cleanup API to wt_status_print Jeff Hostetler
2016-08-11 14:45 ` [PATCH v6 3/9] status: support --porcelain[=<version>] Jeff Hostetler
2016-08-11 14:45 ` [PATCH v6 4/9] status: collect per-file data for --porcelain=v2 Jeff Hostetler
2016-08-11 14:45 ` [PATCH v6 5/9] status: print per-file porcelain v2 status data Jeff Hostetler
2016-08-11 14:45 ` [PATCH v6 6/9] status: print branch info with --porcelain=v2 --branch Jeff Hostetler
2016-08-11 14:46 ` [PATCH v6 7/9] git-status.txt: describe --porcelain=v2 format Jeff Hostetler
2016-08-11 14:46 ` [PATCH v6 8/9] test-lib-functions.sh: Add lf_to_nul Jeff Hostetler
2016-08-11 14:46 ` [PATCH v6 9/9] status: unit tests for --porcelain=v2 Jeff Hostetler
2016-08-11 18:36 ` Junio C Hamano
2016-08-11 20:51 ` Jeff Hostetler
2016-08-11 18:59 ` 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=xmqqinv7168i.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=jeffhost@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.