From: Felipe Contreras <felipe.contreras@gmail.com>
To: git@vger.kernel.org
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [ANN] git-branch-list 0.1 released
Date: Fri, 25 Jun 2021 11:21:18 -0500 [thread overview]
Message-ID: <60d6027e6cf05_c746208af@natae.notmuch> (raw)
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
reply other threads:[~2021-06-25 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=60d6027e6cf05_c746208af@natae.notmuch \
--to=felipe.contreras@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.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).