Re: gitk pull request // was: Re: gitk: "lime" color incompatible with older Tk versions
- From
Paul Mackerras <paulus@ozlabs.org>
- Date
- Jan 16, 2017, 03:17 UTC
- Message-ID
- <20170116031706.GA3322@fergus.ozlabs.ibm.com>
- In-Reply-To
- <xmqq37gldp8g.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Sat, Jan 14, 2017 at 06:35:43PM -0800, Junio C Hamano wrote:
Show 33 quoted lines
> David Aguilar <davvid@gmail.com> writes: > > > On Fri, Jan 13, 2017 at 03:20:43AM -0800, David Aguilar wrote: > >> > >> Ping.. it would be nice to get this patch applied. > > > > Sorry for the noise, and thank you Paul for the fix. > > This was already fixed by Paul in gitk@22a713c72df. > > > > I'm sure Junio will merge gitk.git into git.git soon enough so I > > can sit tight until then, but while I'm here I might as well > > send out a pull request: > > > > The following changes since commit 22a713c72df8b6799c59287c50cee44c4a6db51e: > > > > gitk: Follow themed bgcolor in help dialogs (2016-03-19 14:12:21 +1100) > > > > are available in the git repository at: > > > > git://ozlabs.org/~paulus/gitk.git > > > > for you to fetch changes up to fbf426478e540f4737860dae622603cc0daba3d2: > > > > gitk: Update copyright notice to 2016 (2016-12-12 20:46:42 +1100) > > Pinging Paul to signal me that his tree is ready to pull from is > appreciated, and asking Paul if his tree is ready to be pulled and > then relaying his answer to me is also fine, but I am sensing that > this message is neither. So let me double check. > > Paul, is it a good time to pull, or do you still have something not > published yet that should go together with what you have already > queued?
I recently pushed out one more commit to update the Russian translation from Dimitriy Ryazantcev. The head is now 8fef3f36b779. I have a couple more series that I am currently reviewing, but nothing immediately ready to publish. It would be a good time for you to do a pull, since the "lime" color fix and the memory consumption fixes should be helpful for a lot of people.
Thanks, Paul.