From: Paul Mackerras <paulus@ozlabs.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFPR] updates for 2.7?
Date: Sat, 19 Dec 2015 14:35:42 +1100 [thread overview]
Message-ID: <20151219033542.GF422@fergus.ozlabs.ibm.com> (raw)
In-Reply-To: <xmqqtwnjcnrb.fsf@gitster.mtv.corp.google.com>
On Tue, Dec 15, 2015 at 03:09:44PM -0800, Junio C Hamano wrote:
> Git 2.7-rc1 has just been tagged, and the remainder of the year will
> be for the stabilization, fixes to brown-paper-bag bugs, reverts of
> regressions, etc., but I haven't seen updates to the various
> subsystems you guys maintain for some time. Please throw me "this
> is a good time to pull and here are the updates" message in the
> coming few weeks.
Please do a pull from git://ozlabs.org/~paulus/gitk.git to get:
* Some improvements to gitk appearance, particularly on high DPI monitors
* Translation updates for Japanese and Swedish.
Thanks,
Paul.
next prev parent reply other threads:[~2015-12-19 3:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 23:09 [RFPR] updates for 2.7? Junio C Hamano
2015-12-16 1:00 ` Eric Wong
2015-12-19 3:35 ` Paul Mackerras [this message]
2015-12-21 16:57 ` Junio C Hamano
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=20151219033542.GF422@fergus.ozlabs.ibm.com \
--to=paulus@ozlabs.org \
--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).