From: Paul Mackerras <paulus@samba.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Marc Branchaud <marcnarc@xiplink.com>,
Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org,
"Lucas Sandery [three am design]" <lucas@threeamdesign.com.au>
Subject: Re: [PATCHv2] gitk: Replace "next" and "prev" buttons with down and up arrows.
Date: Thu, 23 Jan 2014 22:08:48 +1100 [thread overview]
Message-ID: <20140123110847.GA12814@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <xmqqa9enydm4.fsf@gitster.dls.corp.google.com>
On Wed, Jan 22, 2014 at 12:18:27PM -0800, Junio C Hamano wrote:
> Is this a good time for me to pull from you? I see these on your
> 'master' branch.
>
> 8f86339 gitk: Comply with XDG base directory specification
> 786f15c gitk: Replace "next" and "prev" buttons with down and up arrows
> c61f3a9 gitk: chmod +x po2msg.sh
> 6c626a0 gitk: Update copyright dates
> 45f884c gitk: Add Bulgarian translation (304t)
> 1f3c872 gitk: Fix mistype
>
> Thanks.
Yes, please pull. I have just pushed one more:
76d64ca gitk: Indent word-wrapped lines in commit display header
Thanks,
Paul.
next prev parent reply other threads:[~2014-01-23 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 2:31 gitk next/prev buttons Lucas Sandery [three am design]
2013-10-02 1:08 ` Lucas Sandery
2013-10-08 17:50 ` Marc Branchaud
2013-10-08 19:36 ` Jonathan Nieder
2013-10-08 20:45 ` Marc Branchaud
2013-12-18 16:04 ` [PATCHv2] gitk: Replace "next" and "prev" buttons with down and up arrows Marc Branchaud
2014-01-21 15:33 ` Marc Branchaud
2014-01-22 11:04 ` Paul Mackerras
2014-01-22 20:18 ` Junio C Hamano
2014-01-23 11:08 ` Paul Mackerras [this message]
2014-01-23 16:51 ` Junio C Hamano
2013-10-08 20:49 ` [PATCH] gitk: Rename "next" and "prev" buttons to "older" and "newer" Marc Branchaud
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=20140123110847.GA12814@iris.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=lucas@threeamdesign.com.au \
--cc=marcnarc@xiplink.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.