From: Marc Branchaud <marcnarc@xiplink.com>
To: Michael Haggerty <mhagger@alum.mit.edu>,
Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 00/13] gitk: tweak rendering of remote-tracking references
Date: Mon, 6 Feb 2017 12:13:19 -0500 [thread overview]
Message-ID: <19aa8a8f-6f5e-ac90-277c-94d2b0caaa9a@xiplink.com> (raw)
In-Reply-To: <cover.1482164633.git.mhagger@alum.mit.edu>
On 2016-12-19 11:44 AM, Michael Haggerty wrote:
> This patch series changes a bunch of details about how remote-tracking
> references are rendered in the commit list of gitk:
I don't see this series in git v2.12.0-rc0, nor in Paul's gitk repo.
I hope this is an oversight, and not that the series got dropped for
some reason.
M.
> * Omit the "remote/" prefix on normal remote-tracking references. They
> are already distinguished via their two-tone rendering and (usually)
> longer names, and this change saves a lot of visual clutter and
> horizontal space.
>
> * Render remote-tracking references that have more than the usual
> three slashes like
>
> origin/foo/bar
> ^^^^^^^
>
> rather than
>
> origin/foo/bar (formerly remotes/origin/foo/bar)
> ^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^
>
> , where the indicated part is the prefix that is rendered in a
> different color. Usually, such a reference represents a remote
> branch that contains a slash in its name, so the new split more
> accurately portrays the separation between remote name and remote
> branch name.
>
> * Introduce a separate constant to specify the background color used
> for the branch name part of remote-tracking references, to allow it
> to differ from the color used for local branches (which by default
> is bright green).
>
> * Change the default background colors for remote-tracking branches to
> light brown and brown (formerly they were pale orange and bright
> green).
>
> I understand that the colors of pixels on computer screens is an even
> more emotional topic that that of bikesheds, so I implemented the last
> change as a separate commit, the last one in the series. Feel free to
> drop it if you don't want the default color change.
>
> Along the way, I did a bunch of refactoring in the area to make these
> changes easier, and introduced a constant for the background color of
> "other" references so that it can also be adjusted by users.
>
> (Unfortunately, these colors can only be adjusted by editing the
> configuration file. Someday it would be nice to allow them to be
> configured via the preferences dialog.)
>
> It's been a while since I've written any Tcl code, so I apologize in
> advance for any howlers :-)
>
> This branch applies against the `master` branch in
> git://ozlabs.org/~paulus/gitk.
>
> Michael
>
> Michael Haggerty (13):
> gitk: when processing tag labels, don't use `marks` as scratch space
> gitk: keep track of tag types in a separate `types` array
> gitk: use a type "tags" to indicate abbreviated tags
> gitk: use a type "mainhead" to indicate the main HEAD branch
> gitk: fill in `wvals` as the tags are first processed
> gitk: simplify regexp
> gitk: extract a method `remotereftext`
> gitk: only change the color of the "remote" part of remote refs
> gitk: shorten labels displayed for modern remote-tracking refs
> gitk: use type "remote" for remote-tracking references
> gitk: introduce a constant otherrefbgcolor
> gitk: add a configuration setting `remoterefbgcolor`
> gitk: change the default colors for remote-tracking references
>
> gitk | 114 ++++++++++++++++++++++++++++++++++++++++++++-----------------------
> 1 file changed, 76 insertions(+), 38 deletions(-)
>
prev parent reply other threads:[~2017-02-06 17:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 16:44 [PATCH 00/13] gitk: tweak rendering of remote-tracking references Michael Haggerty
2016-12-19 16:45 ` [PATCH 01/13] gitk: when processing tag labels, don't use `marks` as scratch space Michael Haggerty
2016-12-19 16:45 ` [PATCH 02/13] gitk: keep track of tag types in a separate `types` array Michael Haggerty
2016-12-19 16:45 ` [PATCH 03/13] gitk: use a type "tags" to indicate abbreviated tags Michael Haggerty
2016-12-19 16:45 ` [PATCH 04/13] gitk: use a type "mainhead" to indicate the main HEAD branch Michael Haggerty
2016-12-19 16:45 ` [PATCH 05/13] gitk: fill in `wvals` as the tags are first processed Michael Haggerty
2016-12-19 16:45 ` [PATCH 06/13] gitk: simplify regexp Michael Haggerty
2016-12-19 16:45 ` [PATCH 07/13] gitk: extract a method `remotereftext` Michael Haggerty
2016-12-19 16:45 ` [PATCH 08/13] gitk: only change the color of the "remote" part of remote refs Michael Haggerty
2016-12-19 16:45 ` [PATCH 09/13] gitk: shorten labels displayed for modern remote-tracking refs Michael Haggerty
2016-12-19 16:45 ` [PATCH 10/13] gitk: use type "remote" for remote-tracking references Michael Haggerty
2016-12-19 16:45 ` [PATCH 11/13] gitk: introduce a constant otherrefbgcolor Michael Haggerty
2016-12-19 16:45 ` [PATCH 12/13] gitk: add a configuration setting `remoterefbgcolor` Michael Haggerty
2016-12-19 16:45 ` [PATCH 13/13] gitk: change the default colors for remote-tracking references Michael Haggerty
2016-12-19 22:53 ` [PATCH 00/13] gitk: tweak rendering of " Philip Oakley
2016-12-20 8:03 ` Michael Haggerty
2016-12-20 15:01 ` Marc Branchaud
2016-12-20 22:17 ` Paul Mackerras
2016-12-20 22:53 ` Marc Branchaud
2016-12-21 0:05 ` Michael Haggerty
2016-12-21 19:07 ` Marc Branchaud
2016-12-22 8:15 ` Michael Haggerty
2017-01-09 22:03 ` Marc Branchaud
2017-02-06 17:13 ` Marc Branchaud [this message]
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=19aa8a8f-6f5e-ac90-277c-94d2b0caaa9a@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=paulus@samba.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).