git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Lehmann <Jens.Lehmann@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2013, #07; Wed, 28)
Date: Fri, 30 Aug 2013 22:04:51 +0200	[thread overview]
Message-ID: <5220FAE3.1070101@web.de> (raw)
In-Reply-To: <xmqqtxi9761a.fsf@gitster.dls.corp.google.com>

Am 29.08.2013 01:24, schrieb Junio C Hamano:
> * bc/submodule-status-ignored (2013-08-20) 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'.

Looks like you didn't merge it to next yet, please don't until we
sorted out the quoting issue Matthieu just brought up.

      parent reply	other threads:[~2013-08-30 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28 23:24 What's cooking in git.git (Aug 2013, #07; Wed, 28) Junio C Hamano
2013-08-29  1:14 ` Kyle J. McKay
2013-08-29  7:20 ` Matthieu Moy
2013-08-29  7:45   ` Stefan Beller
2013-08-30 20:04 ` Jens Lehmann [this message]

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=5220FAE3.1070101@web.de \
    --to=jens.lehmann@web.de \
    --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).