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
Llayer <layer@known.net>
Date
May 14, 2009, 05:21 UTC
Message-ID
<20329.1242278469@relay.known.net>
In-Reply-To
<32541b130905132158s44cc5b19n974901c05cf025b2@mail.gmail.com>
Avery Pennarun <apenwarr@gmail.com> wrote:
>> Short answer:
>> 
>>    git fetch origin
I wasn't doing exactly this, but I was doing the equivalent of 
  git fetch $(git config --get remote.origin.url)
Why would these be different?
Kevin
Previous: layerNext: Avery Pennarun
Message 5 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.