Re: [RFC/PATCH] commit/status: show the index-worktree with -v -v

From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, Matthieu Moy <Matthieu.Moy@imag.fr>,
	Ivo Anjo <ivo.anjo@ist.utl.pt>
Subject: Re: [RFC/PATCH] commit/status: show the index-worktree with -v -v
Date: Thu, 15 Jan 2015 12:38:10 -0800	[thread overview]
Message-ID: <xmqqoapz6aq5.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqq1tmv7qjg.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Thu, 15 Jan 2015 12:11:15 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> I do not think that output order is very helpful.  Two diffs to the
> same file next to each other may make it easier to notice, though.
> ...
> or it may want to even be like this:
>
> 	  diff --git a/A b/A
>         ...
>         diff --git to-be-committed/A left-out-of-the-commit/A
>         ...
>         diff --git a/B b/B
>         ...
>
> by using a custom, unusual and easy-to-notice prefixes.

FWIW, with such a loud custom prefixes, I think it is OK to have all
the changes to be committed first and then everything that is left
out at the end.