From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Subject: Re: What's cooking in git.git (Sep 2013, #02; Mon, 9)
Date: Sun, 22 Sep 2013 15:00:28 +0200 [thread overview]
Message-ID: <523EE9EC.9040207@web.de> (raw)
In-Reply-To: <xmqqhadfp1nx.fsf@gitster.dls.corp.google.com>
Am 21.09.2013 00:29, schrieb Junio C Hamano:
> Jens Lehmann <Jens.Lehmann@web.de> writes:
>
>> Am 10.09.2013 00:53, schrieb Junio C Hamano:
>>> * bc/submodule-status-ignored (2013-09-04) 2 commits
>>> - submodule: don't print status output with ignore=all
>>> - submodule: fix confusing variable name
>>>
>>> Originally merged to 'next' on 2013-08-22
>>>
>>> Will merge to 'next'.
>>
>> I propose to cook this some time in next to give submodule
>> users who have configured ignore=all the opportunity to test
>> and comment on that. And as Matthieu noticed the documentation
>> is not terribly clear here, I'll prepare one or two patches to
>> fix that which should go in together with these changes.
>
> The patches are still in 'next' but I think with the documentation
> update you and Matthieu did, it should be ready to be in 'master'
> now, no?
No objections from my side as nobody reported any problems during
the month that series cooked in next.
next prev parent reply other threads:[~2013-09-22 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 22:53 What's cooking in git.git (Sep 2013, #02; Mon, 9) Junio C Hamano
2013-09-10 8:10 ` Matthieu Moy
2013-09-10 18:31 ` Junio C Hamano
2013-09-10 16:27 ` Jens Lehmann
2013-09-10 18:31 ` Junio C Hamano
2013-09-11 19:07 ` [PATCH] Improve documentation concerning the status.submodulesummary setting Jens Lehmann
2013-09-11 19:58 ` Matthieu Moy
2013-09-20 22:29 ` What's cooking in git.git (Sep 2013, #02; Mon, 9) Junio C Hamano
2013-09-22 13:00 ` Jens Lehmann [this message]
2013-09-22 17:06 ` Matthieu Moy
2013-09-11 21:33 ` Stefan Beller
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=523EE9EC.9040207@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).