
About the same time you were sending this, a co-worker was telling me about the virtues of "git fetch" as opposed to "git pull" which I've used almost exclusively. It makes a lot more sense now, thanks. To everyone who answered: I think we can consider my problems (at least the git ones!) solved, and many thanks. On 6 March 2015 at 12:21, Tim Tisdall <tisdall@gmail.com> wrote:
On Fri, Mar 6, 2015 at 10:29 AM, Giles Orr <gilesorr@gmail.com> wrote:
"git status" usually says "Your branch is up-to-date with 'origin/master'" (or "ahead"), but occasionally - even though origin is configured properly - this line doesn't appear. Is there a way to convince it to always show this line?
Unfortunately, "git status" doesn't seem to ever notice if you're "behind" origin, thus the need for "git remote show origin". Any fix for that?
`git status` only looks at what's on your local file system. You need to first do a `git fetch` to update your local information (doesn't change your code, just git's information), then `git status` will reflect what's actually happening. Without some command that fetches things from the remote, `git status` will always say you're up-to-date (or ahead if you've committed things). --- Talk Mailing List talk@gtalug.org http://gtalug.org/mailman/listinfo/talk
-- Giles http://www.gilesorr.com/ gilesorr@gmail.com