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

Re: "git pull . <branch>" versus "git merge <branch>"

From
RHRene Herman <rene.herman@keyaccess.nl>
Date
Jun 12, 2008, 00:56 UTC
Message-ID
<48507454.2070506@keyaccess.nl>
In-Reply-To
<237967ef0806111449i7d23976dxa3290eece06b5876@mail.gmail.com>
On 11-06-08 23:49, Mikael Magnusson wrote:
> For me, git-pull is that additional command, and using git-pull . 
> <branch> to merge feels really really strange. Why would I pull
> something I already have?

For what it's worth I (as thread starter) agree with this. At least in my mind local and remote branches are very different and I do not mind having to "fetch" the latter first before merging (nor combine the two through a "pull").

I can see the reason for the other viewpoint as well since it emphasises a point about local and remote branches _not_ being very different after all but that's more a symmetry to the implementor than it is to a user I feel. For the user, local and remote branches just are different.

And as such I feel it actually helps to just use "merge". Thanks for the answers everyone -- this was a matter of a user worrying that he wasn't getting it...

Rene
Previous: Mikael MagnussonNext: Junio C Hamano
Message 14 of 16 in “"git pull . <branch>" versus "git merge <branch>"”
  1. Rene HermanJun 11, 2008
  2. David SymondsJun 11, 2008
  3. Rene HermanJun 11, 2008
  4. Miklos VajnaJun 11, 2008
  5. Rene HermanJun 11, 2008
  6. Paolo BonziniJun 11, 2008
  7. Rene HermanJun 11, 2008
  8. Paolo BonziniJun 11, 2008
  9. Daniel BarkalowJun 11, 2008
  10. Brandon CaseyJun 11, 2008
  11. Daniel BarkalowJun 11, 2008
  12. Brandon CaseyJun 11, 2008
  13. Mikael MagnussonJun 11, 2008
  14. Rene HermanJun 12, 2008
  15. Junio C HamanoJun 11, 2008
  16. Rene HermanJun 12, 2008

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.