On Mon, Apr 06, 2009 at 10:30:21AM +0200, Paolo Ciarrocchi wrote:
> I often act like a GIT "evangelist" trying to help friends and
> colleagues in starting using GIT and one of the "complaint" I'm
> getting is that people expect to get this information out of the
> branch command.
>
> I mean something like:
> $ git branch
> * foo <-> origin/foo
>
> What do you think?
Ah. Well, if you just want it for human consumption, that is much
easier. :) That information is already shown by "git status":
$ git status
# On branch next
# Your branch is ahead of 'origin/next' by 8 commits.
...
"git branch -v" is already looking at the information, but it
prints only the "ahead/behind" summary. E.g.,:
$ git branch -v
bar 1e0672d [behind 5] some commit
* baz dccc1cd [ahead 1, behind 3] other commit
foo 787d5a8 [ahead 1] another commit
master a0e632e actual upstream master
It would be pretty trivial to make it do something fancier. The
(extremely rough) patch below shows the tracking branch when
double-verbosity is given:
$ git branch -vv
* next 2d44318 [origin/next: ahead 9] branch -vv wip
So the questions are:
- is this worth it? The verbose information is already available via
git status, but only for the current branch.
- should it be the default with "-v", or require "-vv"? It take up a
bit of screen real estate, which is already in short supply for
"branch -v"
- in both the "status" and "branch" cases, we show nothing if they
are equivalent. I guess you would want to see
* next 2d44318 [origin/next] branch -vv wip
or
* next 2d44318 [origin/next: uptodate] branch -vv wip
-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html