Re: [PATCH v1 0/6] Porcelain Status V2

2016-07-21 Thread Johannes Schindelin
Hi Peff & Jeff ;-) On Wed, 20 Jul 2016, Jeff King wrote: > On Wed, Jul 20, 2016 at 03:27:45PM -0400, Jeff Hostetler wrote: > > > > A totally reasonable response is "haha no. Please stop moving the > > > goalposts". I just wanted to throw it out there as an option (and in > > > case you are inter

Re: [PATCH v1 0/6] Porcelain Status V2

2016-07-20 Thread Jeff King
On Wed, Jul 20, 2016 at 03:27:45PM -0400, Jeff Hostetler wrote: > > A totally reasonable response is "haha no. Please stop moving the > > goalposts". I just wanted to throw it out there as an option (and in > > case you are interested, to let you think about it before any more work > > goes into t

Re: [PATCH v1 0/6] Porcelain Status V2

2016-07-20 Thread Jeff Hostetler
On 07/20/2016 12:15 PM, Jeff King wrote: One final bit of food for thought. Just yesterday somebody asked me about renewing the old idea of using a more standardized format for machine-readable output, like --json. That's obviously something that would exist alongside the existing formats for

Re: [PATCH v1 0/6] Porcelain Status V2

2016-07-20 Thread Jeff King
On Tue, Jul 19, 2016 at 06:10:52PM -0400, Jeff Hostetler wrote: > This patch series adds porcelain V2 format to status. > This provides detailed information about file changes > and about the current branch. > > The new output is accessed via: > git status --porcelain=2 [--branch] > > An ear

[PATCH v1 0/6] Porcelain Status V2

2016-07-19 Thread Jeff Hostetler
This patch series adds porcelain V2 format to status. This provides detailed information about file changes and about the current branch. The new output is accessed via: git status --porcelain=2 [--branch] An earlier draft of this work was submitted under the "Add very verbose porcelain outpu