The following message is a courtesy copy of an article
that has been posted to gmane.comp.version-control.git as well.
Junio C Hamano gits...@pobox.com writes:
Thomas Ackermann th.ac...@arcor.de writes:
But for the simple use case where you only have a master
branch I consider it not really
correctly reports
you're behind.
---
Thomas
- Original Nachricht
Von: Jiang Xin worldhello@gmail.com
An: Thomas Ackermann th.ac...@arcor.de
Datum: 06.01.2014 06:31
Betreff: Re: [Bug report] 'git status' always says Your branch is up-to-date
with 'origin/master
2014/1/6 Thomas Ackermann th.ac...@arcor.de:
Hi Jiang,
this happens with all of my repo clones (I am using V1.8.5.2
on Windows and on Linux). Steps to reproduce:
mkdir repo_a cd repo_a git init .
echo 1foo git add foo git commit -m 1
cd ..
git clone repo_a repo_b
cd repo_a
echo
Unfortunately that's not true. In repo_b your ref for origin/master
has not moved. It has remotely (meaning refs/heads/master in repo_a
has moved), but git status is not hitting the remote to find out; it
only looks at the local state. To see what I mean, run git fetch in
repo_b. Once you
Hi,
Thomas Ackermann wrote:
In repo_b your ref for origin/master
has not moved. It has remotely (meaning refs/heads/master in repo_a
has moved), but git status is not hitting the remote to find out; it
only looks at the local state.
[...]
But for the simple
But for the simple use case where you only have a master
branch I consider it not really helpful and - at least for me -
misleading.
I see what you mean, and you're not the only one.
Git follows a rule of never contact another machine unless explicitly
asked to using a command such
6 matches
Mail list logo
