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

Re: how to update origin/<branch> after a push to origin <branch>?

From
Avery Pennarun <apenwarr@gmail.com>
Date
May 14, 2009, 04:58 UTC
Message-ID
<32541b130905132158s44cc5b19n974901c05cf025b2@mail.gmail.com>
In-Reply-To
<19640.1242276135@relay.known.net>
On Thu, May 14, 2009 at 12:42 AM, layer <layer@known.net> wrote:
Show 12 quoted lines
> after the push, I still see the names of the files I pushed because I
> haven't updated origin/master yet, with a fetch.  Of course, a "git
> pull" would do it, but I don't want to do that, because I might be
> using something other than `origin' and I don't want anything but the
> single branch.
>
> So, I naively thought that
>
>  git fetch origin master
>
> would do the trick, but after that command the git diff above still
> shows the same files.
Short answer:
   git fetch origin

However, 'git push origin master' should update origin/master automatically, at least in relatively recent git versions. It's rather weird if that didn't happen.

Have fun,
Avery
Previous: layerNext: layer
Message 2 of 6 in “how to update origin/<branch> after a push to origin <branch>?”
  1. layerMay 14, 2009
  2. Avery PennarunMay 14, 2009
  3. layerMay 14, 2009
  4. layerMay 14, 2009
  5. layerMay 14, 2009
  6. Avery PennarunMay 14, 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.