From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2013, #01; Tue, 3)
Date: Wed, 04 Sep 2013 22:52:33 +0200 [thread overview]
Message-ID: <52279D91.2030802@web.de> (raw)
In-Reply-To: <xmqqfvtkmm2d.fsf@gitster.dls.corp.google.com>
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).
next prev parent reply other threads:[~2013-09-04 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 23:00 What's cooking in git.git (Sep 2013, #01; Tue, 3) Junio C Hamano
2013-09-04 9:01 ` Jeff King
2013-09-04 11:50 ` Matthieu Moy
2013-09-04 19:19 ` Junio C Hamano
2013-09-04 20:52 ` Jens Lehmann [this message]
2013-09-05 6:32 ` Matthieu Moy
2013-09-06 2:11 ` Jiang Xin
2013-09-06 16:28 ` Junio C Hamano
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=52279D91.2030802@web.de \
--to=jens.lehmann@web.de \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).