Jiang Xin writes:
> 2013/8/26 Jeremy Rosen :
>>
>> nitpicking, but shouldn't this be worded as "up to date" rather than
>> "identical" ?
>>
>> The reason is that identical gives the idea that the two branch happen to be
>> on the same
>> commit wheras "up to date" gives the idea that there is a
2013/8/26 Jeremy Rosen :
>
> nitpicking, but shouldn't this be worded as "up to date" rather than
> "identical" ?
>
> The reason is that identical gives the idea that the two branch happen to be
> on the same
> commit wheras "up to date" gives the idea that there is a special
> relationship betw
>
> But this will not work if there is no change between the current
> branch and its upstream. Always report upstream tracking info
> even if there is no difference, so that "git status" is consistent
> for checking tracking info for current branch. E.g.
>
> $ git status
> # On branch fe
In order to see what the current branch is tracking, one way is using
"git branch -v -v", but branches other than the current are also
reported. Another way is using "git status", such as:
$ git status
# On branch master
# Your branch is ahead of 'origin/master' by 1 commit.
...
B
4 matches
Mail list logo
