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

Re: git pull origin doesn't update the master

From
Junio C Hamano <junkio@cox.net>
Date
Apr 10, 2006, 07:24 UTC
Message-ID
<7vmzetao5h.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<cc723f590604092345r7d0e2cedr8f9838d054ecb023@mail.gmail.com>
"Aneesh Kumar" <aneesh.kumar@gmail.com> writes:
> Work flow is now a bit complicated. I clone the repository. Now i need
> to edit remotes/origin to make sure what all branches i need to
> follow. And then do a git pull origin. Earlier i just need to do a
> clone and a git pull. I don't need to fast forward pu branch.

What you are saying is that the previous round did a wrong thing without telling the user, and it just happened that you did not care about the wrong thing it did.

It is a gentle reminder that heads that are rewound need to be advertised as such. It is conceivable that in future versions of git we might want to be able to mark some branches "this is expected to be rewound" explicitly and make the clone operation to take notice, to give you the plus sign automatically.

Previous: Aneesh Kumar
Message 6 of 6 in “git pull origin doesn't update the master”
  1. Aneesh KumarApr 10, 2006
  2. Aneesh KumarApr 10, 2006
  3. seanApr 10, 2006
  4. Junio C HamanoApr 10, 2006
  5. Aneesh KumarApr 10, 2006
  6. Junio C HamanoApr 10, 2006

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.