Re: git-branch --print-current

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Alexandre Dulaunoy
Date: Sunday, January 4, 2009 - 3:07 am

On Fri, Jan 2, 2009 at 4:28 AM, Karl Chen <quarl@cs.berkeley.edu> wrote:

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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
git-branch --print-current, Karl Chen, (Thu Jan 1, 8:28 pm)
Re: git-branch --print-current, David Aguilar, (Thu Jan 1, 9:26 pm)
Re: git-branch --print-current, Karl Chen, (Sat Jan 3, 7:18 pm)
Re: git-branch --print-current, Miklos Vajna, (Sat Jan 3, 8:38 pm)
Re: git-branch --print-current, Karl Chen, (Sat Jan 3, 9:26 pm)
Re: git-branch --print-current, Junio C Hamano, (Sat Jan 3, 10:17 pm)
Re: git-branch --print-current, Arnaud Lacombe, (Sun Jan 4, 1:21 am)
Re: git-branch --print-current, Alexandre Dulaunoy, (Sun Jan 4, 3:07 am)
Re: git-branch --print-current, demerphq, (Sun Jan 4, 5:31 am)
Re: git-branch --print-current, Karl Chen, (Sun Jan 4, 5:40 am)
Re: git-branch --print-current, demerphq, (Sun Jan 4, 5:49 am)
Re: git-branch --print-current, demerphq, (Sun Jan 4, 6:35 am)
Re: git-branch --print-current, Arnaud Lacombe, (Sun Jan 4, 10:55 am)
Re: git-branch --print-current, Adeodato , (Sun Jan 4, 11:02 am)
Re: git-rev-parse --symbolic-abbrev-name, Junio C Hamano, (Sun Jan 4, 12:36 pm)
Re: git-rev-parse --symbolic-abbrev-name, Arnaud Lacombe, (Sun Jan 4, 1:23 pm)
Re: git-branch --print-current, Jakub Narebski, (Sun Jan 4, 2:48 pm)
Re: git-rev-parse --symbolic-abbrev-name, Miklos Vajna, (Sun Jan 4, 3:38 pm)
Re: git-branch --print-current, Junio C Hamano, (Sun Jan 4, 5:41 pm)
Re: git-branch --print-current, Shawn O. Pearce, (Sun Jan 4, 7:18 pm)
Re: git-branch --print-current, Junio C Hamano, (Sun Jan 4, 8:55 pm)
Re: git-rev-parse --symbolic-abbrev-name, Arnaud Lacombe, (Sun Jan 4, 10:35 pm)
Re: git-branch --print-current, Jeff King, (Sun Jan 4, 10:50 pm)
Re: git-rev-parse --symbolic-abbrev-name, Miklos Vajna, (Sun Jan 4, 11:45 pm)