From: Paul Mackerras <paulus@samba.org>
To: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Chances of getting gitk series merged
Date: Mon, 12 Sep 2011 14:32:10 -0300 [thread overview]
Message-ID: <20110912173210.GA11134@bloggs.ozlabs.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1109082055560.12564@debian>
On Thu, Sep 08, 2011 at 09:08:57PM -0400, Martin von Zweigbergk wrote:
> I was happy to see in another thread that you are still here. If I
> understand correctly, you are the maintainer of gitk, meaning that all
> gitk patches go through you and then Junio pulls from you. I have this
> series [1] that I sent in out in April that I would like to get
> merged. Could you have a look at it?
I actually applied the series and I believe I pushed it out, but with
master.kernel.org being down I can't check. I got distracted before
asking Junio to pull, though.
Paul.
prev parent reply other threads:[~2011-09-12 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 1:08 Chances of getting gitk series merged Martin von Zweigbergk
2011-09-12 17:32 ` 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=20110912173210.GA11134@bloggs.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=martin.von.zweigbergk@gmail.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).