git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/2] gitk: alter the ordering for the "Tags and heads" view

From
Michael Rappazzo <rappazzo@gmail.com>
Date
Mar 9, 2016, 18:18 UTC
Message-ID
<1457547490-12249-1-git-send-email-rappazzo@gmail.com>

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: Michael Rappazzo
Message 1 of 3 in “gitk: alter the ordering for the "Tags and heads" view”
  1. 0/2 gitk: alter the ordering for the "Tags and heads" viewMichael Rappazzo, Mar 9, 2016
  2. 1/2 gitk: alter the ordering for the "Tags and heads" viewMichael Rappazzo, Mar 9, 2016
  3. 2/2 gitk: add an option to enable sorting the "Tags and heads" view by ref typeMichael Rappazzo, Mar 9, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.