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

[ANN] git-branch-list 0.1 released

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Jun 25, 2021, 16:21 UTC
Message-ID
<60d6027e6cf05_c746208af@natae.notmuch>

The current version of `git branch --list` mostly works, but it's slow and cumbersome. While this could easily be fixed in git itself, every patch that tries to improve the user interface is de facto rejected [1].

An external command `git branch-list` is the solution.
Why is `git branch-list` better?
 1. It provides useful information at all verbosity levels
 2. It does not clutter the output with unhelpful characters
 3. It provides a more consistent output
 4. It sorts branches by default
 5. It filters branches more conveniently
 6. It tracks branches in a simpler way
 7. It's way faster
== Verbosity levels ==
At level 0:
 * master origin/master
At level 1:
 * master [origin/master] The first batch post Git 2.32

What about the tracking information? That's orthogonal in `git branch-list`, and simplified:

 % git branch-list -t
 * master origin/master=
== Performance ==

Using 100 random branches on Linux with random commits over the past decade:

 % git branch --list --verbose
 21.611 seconds
 % git branch-list
 0.106 seconds
Grab it from my GitHub repository:
https://github.com/felipec/git-branch-list
Cheers.
[1] https://lore.kernel.org/git/YL8KiiGXF8LdGmQ2@coredump.intra.peff.net/
-- 
Felipe Contreras
Message 1 of 1 in “[ANN] git-branch-list 0.1 released”
  1. Felipe ContrerasJun 25, 2021

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.