git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Thomas Ackermann <th.acker@arcor.de>
Cc: bturner@atlassian.com, worldhello.net@gmail.com,
	git@vger.kernel.org, gitster@pobox.com
Subject: Re: Re: Re: [Bug report] 'git status' always says "Your branch is up-to-date with 'origin/master'"
Date: Mon, 6 Jan 2014 07:45:52 -0800	[thread overview]
Message-ID: <20140106154552.GA22189@google.com> (raw)
In-Reply-To: <1283978462.720554.1388999328222.JavaMail.ngmail@webmail15.arcor-online.net>

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 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 as 'git pull' or 'git fetch'".  To
support this, it makes a distinction between (1) the remote-tracking
ref origin/master and (2) the actual branch "master" in the remote
repository.  The former is what is updated by 'git fetch', and the
latter is something git does not know about without talking to the
remote server.

What documentation did you use when first starting to learn git?
Perhaps it can be fixed to emphasize the distinction between (1) and
(2) earlier.

Thanks,
Jonathan

  reply	other threads:[~2014-01-06 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06  8:24 Aw: Re: [Bug report] 'git status' always says "Your branch is up-to-date with 'origin/master'" Thomas Ackermann
2014-01-06  8:48 ` Bryan Turner
2014-01-06  9:04 ` Jiang Xin
2014-01-06  9:08 ` Aw: " Thomas Ackermann
2014-01-06 15:45   ` Jonathan Nieder [this message]
2014-01-06 16:00   ` Aw: " Thomas Ackermann
2014-01-06 17:12     ` Junio C Hamano
2014-01-14 23:34       ` Keshav Kini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140106154552.GA22189@google.com \
    --to=jrnieder@gmail.com \
    --cc=bturner@atlassian.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=th.acker@arcor.de \
    --cc=worldhello.net@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).