From: Paul Mackerras <paulus@samba.org>
To: Beat Bolli <dev+git@drbeat.li>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v4] gitk: Add a "Copy commit summary" command
Date: Tue, 21 Jul 2015 20:28:16 +1000 [thread overview]
Message-ID: <20150721102815.GA2571@yogo.paulus.ozlabs.org> (raw)
In-Reply-To: <55AE1CAB.9040404@drbeat.li>
On Tue, Jul 21, 2015 at 12:19:23PM +0200, Beat Bolli wrote:
> Guys,
>
> can I get a Yea or Nay for this patch?
>
> Does it go in via Paul's gitk repo or directly through Junio?
I'll put it in. It goes into my repo and from there into Junio's.
I'm on vacation and travelling this week, so please be patient.
Regards,
Paul.
next prev parent reply other threads:[~2015-07-21 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 11:15 [PATCH v4] gitk: Add a "Copy commit summary" command Beat Bolli
2015-07-21 10:19 ` Beat Bolli
2015-07-21 10:28 ` Paul Mackerras [this message]
2015-07-21 10:30 ` Beat Bolli
2015-08-11 21:00 ` [PATCH] gitk: adjust the menu line numbers to compensate for the new entry Beat Bolli
2015-08-13 7:37 ` [PATCH v4] gitk: Add a "Copy commit summary" command Paul Mackerras
2015-08-13 19:02 ` Beat Bolli
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=20150721102815.GA2571@yogo.paulus.ozlabs.org \
--to=paulus@samba.org \
--cc=dev+git@drbeat.li \
--cc=git@vger.kernel.org \
/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).