Re: What's cooking in git.git (Sep 2013, #01; Tue, 3)

> Am 04.09.2013 21:19, schrieb Junio C Hamano:
>> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
>> 
>>> Junio C Hamano <gitster@pobox.com> writes:
>>>
>>>> * mm/status-without-comment-char (2013-08-29) 5 commits
>>>>  - status: introduce status.displayCommentChar to disable display of #
>>>>  - SQUASH: do not fprintf() random strings
>>>>  - get rid of "git submodule summary --for-status"
>>>>  - wt-status: use argv_array API
>>>>  - builtin/stripspace.c: fix broken indentation
>>>>
>>>>  Allow "git status" to omit the prefix to make its output a comment
>>>>  in a commit log editor, which is not necessary for human
>>>>  consumption.
>>>
>>> I'm waiting for the situation of "git submodule --for-status" to be
>>> settled to send a reroll. Don't merge this for now, and let
>>> bc/submodule-status-ignored converge.
>> 
>> Thanks.  I had an impression that bc/submodule-status-ignored was
>> still being discussed.  Has what I have in 'pu' settled?
>
> Almost (see my other mail concerning bc/submodule-status-ignored).
> If the removal of the --for-status option is reverted from patch #3
> here (which I outlined in $gmane/233764) this series can be merged
> without really depending on bc/submodule-status-ignored (even though
> the temporarily unused --for-status option may look a bit strange
> until the latter is merged).