2013/8/12 Junio C Hamano :
> Jiang Xin writes:
>
>> 2013/8/10 Junio C Hamano :
>>> Jiang Xin writes:
>>>
So always show the remote tracking branch in the output of "git status"
and other commands will help users to see where the current branch
will push to and pull from. E.g.
Jiang Xin writes:
> 2013/8/10 Junio C Hamano :
>> Jiang Xin writes:
>>
>>> So always show the remote tracking branch in the output of "git status"
>>> and other commands will help users to see where the current branch
>>> will push to and pull from. E.g.
>>> ...
>>
>> Hmmph.
>>
>> I do not know
2013/8/10 Junio C Hamano :
> Jiang Xin writes:
>
>> So always show the remote tracking branch in the output of "git status"
>> and other commands will help users to see where the current branch
>> will push to and pull from. E.g.
>> ...
>
> Hmmph.
>
> I do not know if this will help any case you d
Jiang Xin writes:
> If the current branch has an upstream branch, and there are changes
> between the current branch and its upstream, some commands (such as
> "git status", "git status -bs", and "git checkout") will report their
> relationship. E.g.
>
> $ git status
> # On branch master
Changes since v2:
* The return value of function stat_tracking_info() is changed.
When the current branch and its remote tracking branch point
to the same commit, will return 1, instead of 0. Because we
want to report the tracking info for such case.
* Remove duplicated codes in builti
If the current branch has an upstream branch, and there are changes
between the current branch and its upstream, some commands (such as
"git status", "git status -bs", and "git checkout") will report their
relationship. E.g.
$ git status
# On branch master
# Your branch is ahead of 'or
6 matches
Mail list logo
