From: Michael Rappazzo <rappazzo@gmail.com>
To: paulus@samba.org
Cc: git@vger.kernel.org, Michael Rappazzo <rappazzo@gmail.com>
Subject: [PATCH 0/2] gitk: alter the ordering for the "Tags and heads" view
Date: Wed, 9 Mar 2016 13:18:08 -0500 [thread overview]
Message-ID: <1457547490-12249-1-git-send-email-rappazzo@gmail.com> (raw)
In a codebase with a large number of remote branches, the "Tags and heads"
view can split the local refs around the name "remotes". I wanted to make
this view more useful as a quick view of the refs that are important to me
at the moment (the branches that I am actively working on).
This patch series adds a command line option to change the ordering of the
view (`--sort-refs-by-type`) which will sort the refs in the following
order:
local refs
remote refs which are tracked (upstream) by local refs
remote refs
tags
other refs
Each of these lists is independently sorted before being put into the main
ref list. Also note that the upstream refs are _not_ duplicated in the
remote refs list.
Michael Rappazzo (2):
gitk: alter the ordering for the "Tags and heads" view
gitk: add an option to enable sorting the "Tags and heads" view by ref
type
gitk | 59 ++++++++++++++++++++++++++++++++++++++++++++++++++++-------
1 file changed, 52 insertions(+), 7 deletions(-)
--
2.7.2
next reply other threads:[~2016-03-09 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 18:18 Michael Rappazzo [this message]
2016-03-09 18:18 ` [PATCH 1/2] gitk: alter the ordering for the "Tags and heads" view Michael Rappazzo
2016-03-09 18:18 ` [PATCH 2/2] gitk: add an option to enable sorting the "Tags and heads" view by ref type Michael Rappazzo
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=1457547490-12249-1-git-send-email-rappazzo@gmail.com \
--to=rappazzo@gmail.com \
--cc=git@vger.kernel.org \
--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.
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).