git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: problems getting uptodate from a remote repository

From
RHRobert Haines <rhaines@manchester.ac.uk>
Date
May 19, 2009, 17:03 UTC
Message-ID
<ADB06DB0-9198-4AB4-8BE8-6472B943C872@manchester.ac.uk>
In-Reply-To
<9719867c0905190909q74e4a6b9r4857fb6f32ff394@mail.gmail.com>
Hi Aaron,
On 19 May 2009, at 17:09, Aaron Gray wrote:
Show 11 quoted lines
> I have done a 'git fetch' but the repo is not being updated to  
> latest changes.
>
> I am getting the message :-
>
>    "Your branch is behind 'origin/master' by 53 commits, and can be
> fast-forwarded.
>
> when I do a 'git checkout master'
>
> What is going on here and what can I do about it ?
<snip config>

A fetch just updates your remote tracking branches in your local repository, it doesn't merge them as well. To update your local master you would then do (while on branch master):

$ git merge origin/master

This extra step allows you to create a new branch with origin/master as its start point to check that you're happy with the updates before you update your local master should you wish to do so.

Cheers, Rob

Previous: Aaron GrayNext: Sverre Rabbelier
Message 2 of 3 in “Re: problems getting uptodate from a remote repository”
  1. Aaron GrayMay 19, 2009
  2. Robert HainesMay 19, 2009
  3. Sverre RabbelierMay 19, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.