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

Re: git-branch --print-current

From
ADAlexandre Dulaunoy <adulau@gmail.com>
Date
Jan 4, 2009, 10:07 UTC
Message-ID
<1baa801f0901040207r64195594m64359dbc60a5f662@mail.gmail.com>
In-Reply-To
<quack.20090101T1928.lthzliaqtdf@roar.cs.berkeley.edu>
On Fri, Jan 2, 2009 at 4:28 AM, Karl Chen <quarl@cs.berkeley.edu> wrote:
Show 5 quoted lines
>
> How about an option to git-branch that just prints the name of the
> current branch for scripts' sake?  To replace:
>
>    git branch --no-color 2>/dev/null | perl -ne '/^[*] (.*)/ && print $1'

I tend to support your request especially that extracting the current branch is something that is done regularly. Looking in my own scripts/aliases and some of my colleagues, there are plenty of variation using Perl, sed, awk, tr and Python to extract the current branch.

Using git-symbolic-ref is not obvious, especially that the summary/name
 of the man page is :
"git-symbolic-ref - Read and modify symbolic refs"
But the description is pretty clear :

"Given one argument, reads which branch head the given symbolic ref refers to and outputs its path, relative to the .git/ directory. Typically you would give HEAD as the <name> argument to see on which branch your working tree is on."

But naturally, as a lazy user, you will pick git-branch especially that's the tools is listed with the most commonly used git commands with a very attractive description :

"branch     List, create, or delete branches"
On an user perspective, having the option in git-branch seems more natural.
Just a comment,
-- 
--                   Alexandre Dulaunoy (adulau) -- http://www.foo.be/
--                             http://www.foo.be/cgi-bin/wiki.pl/Diary
--         "Knowledge can create problems, it is not through ignorance
--                                that we can solve them" Isaac Asimov
Previous: Jakub NarebskiNext: demerphq
Message 27 of 28 in “git-branch --print-current”
  1. Karl ChenJan 2, 2009
  2. David AguilarJan 2, 2009
  3. Karl ChenJan 4, 2009
  4. Miklos VajnaJan 4, 2009
  5. Karl ChenJan 4, 2009
  6. Junio C HamanoJan 4, 2009
  7. git-rev-parse --symbolic-abbrev-name [was Re: git-branch --print-current]Karl Chen, Jan 4, 2009
  8. demerphqJan 4, 2009
  9. Junio C HamanoJan 4, 2009
  10. Arnaud LacombeJan 4, 2009
  11. Miklos VajnaJan 4, 2009
  12. Arnaud LacombeJan 5, 2009
  13. Miklos VajnaJan 5, 2009
  14. Junio C HamanoJan 6, 2009
  15. Arnaud LacombeJan 7, 2009
  16. demerphqJan 4, 2009
  17. Junio C HamanoJan 5, 2009
  18. Shawn O. PearceJan 5, 2009
  19. Junio C HamanoJan 5, 2009
  20. Jeff KingJan 5, 2009
  21. Arnaud LacombeJan 4, 2009
  22. Karl ChenJan 4, 2009
  23. demerphqJan 4, 2009
  24. Arnaud LacombeJan 4, 2009
  25. Adeodato SimóJan 4, 2009
  26. Jakub NarebskiJan 4, 2009
  27. Alexandre DulaunoyJan 4, 2009
  28. demerphqJan 4, 2009

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.