git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: git@vger.kernel.org
Subject: Re: [GIT PULL] gitk update
Date: Sat, 03 Oct 2020 10:04:28 -0700	[thread overview]
Message-ID: <xmqqy2kn8cmb.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20201003092010.GC3089868@thinks.paulus.ozlabs.org> (Paul Mackerras's message of "Sat, 3 Oct 2020 19:20:10 +1000")

Paul Mackerras <paulus@ozlabs.org> writes:

> Hi Junio,
>
> Whenever it's convenient for you, please do a pull from my gitk
> repository at git://ozlabs.org/~paulus/gitk.git to get 6 commits
> updating gitk.
>
> Thanks,
> Paul.

Will do.  Are these the six you mentioned, or am I missing some
other commits?

    $ git log --first-parent --oneline ..paulus/master
    6cd80496e9 gitk: Resize panes correctly when reducing window size
    e244588eb6 gitk: replace tabs with spaces
    a99bc27aec gitk: fix the context menu not appearing in the presence of submodule diffs
    2faa6cdc5e gitk: Un-hide selection in areas with non-default background color
    113ce1243f gitk: add diff lines background colors
    e272a77964 gitk: be prepared to be run in a bare repository
    c1a63459ed gitk: Preserve window dimensions on exit when not using ttk themes
    f177c49a97 gitk: don't highlight files after submodules as submodules
    d4247e0602 gitk: fix branch name encoding error
    b8b60957ce gitk: rename "commit summary" to "commit reference"

Thanks.

  reply	other threads:[~2020-10-03 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-03  9:20 [GIT PULL] gitk update Paul Mackerras
2020-10-03 17:04 ` Junio C Hamano [this message]
2020-10-06 11:13   ` Paul Mackerras
2020-11-10  0:16     ` Anders Kaseorg
  -- strict thread matches above, loose matches on Subject: below --
2019-09-15 23:33 Paul Mackerras
2019-09-16 17:18 ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqy2kn8cmb.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=paulus@ozlabs.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).