git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>, Mark Hills <mark@pogo.org.uk>,
	Pat Thoyts <patthoyts@users.sourceforge.net>,
	Jonathan Nieder <jrnieder@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH RESEND] Teach gitk to display dirty submodules correctly
Date: Mon, 19 Apr 2010 11:10:32 +1000	[thread overview]
Message-ID: <20100419011032.GB4386@brick.ozlabs.ibm.com> (raw)
In-Reply-To: <7vzl122f6k.fsf@alter.siamese.dyndns.org>

On Sat, Apr 17, 2010 at 09:53:55AM -0700, Junio C Hamano wrote:

> Thanks.  Is it a good time to pull?

Yes, I think so, thanks.

Paul.

      reply	other threads:[~2010-04-19  1:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 20:16 [PATCH RESEND] Teach gitk to display dirty submodules correctly Jens Lehmann
2010-04-17  8:56 ` Paul Mackerras
2010-04-17 16:53   ` Junio C Hamano
2010-04-19  1:10     ` Paul Mackerras [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=20100419011032.GB4386@brick.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=mark@pogo.org.uk \
    --cc=patthoyts@users.sourceforge.net \
    /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).