public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Jens Lehmann <Jens.Lehmann@web•de>
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: Tue, 10 Sep 2013 11:31:55 -0700	[thread overview]
Message-ID: <xmqqk3ioy1d0.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <522F486A.1000705@web.de> (Jens Lehmann's message of "Tue, 10 Sep 2013 18:27:22 +0200")

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.

OK.

Thanks.

  reply	other threads:[~2013-09-10 18:32 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 [this message]
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
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=xmqqk3ioy1d0.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=Jens.Lehmann@web$(echo .)de \
    --cc=Matthieu.Moy@grenoble-inp$(echo .)fr \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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