Jiang Xin worldhello@gmail.com writes:
2013/8/10 Junio C Hamano gits...@pobox.com:
Jiang Xin worldhello@gmail.com 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
2013/8/12 Junio C Hamano gits...@pobox.com:
Jiang Xin worldhello@gmail.com writes:
2013/8/10 Junio C Hamano gits...@pobox.com:
Jiang Xin worldhello@gmail.com writes:
So always show the remote tracking branch in the output of git status
and other commands will help users to see where
2013/8/10 Junio C Hamano gits...@pobox.com:
Jiang Xin worldhello@gmail.com 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
Jiang Xin worldhello@gmail.com 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
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
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
6 matches
Mail list logo
