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

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

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Jun 11, 2008, 17:56 UTC
Message-ID
<alpine.LNX.1.00.0806111340570.19665@iabervon.org>
In-Reply-To
<484F2174.9020508@keyaccess.nl>
On Wed, 11 Jun 2008, Rene Herman wrote:
Show 5 quoted lines
> Good day.
> 
> The manpages seem to be making somewhat of a point of mentioning "git pull .
> <branch>" as the way to merge a local branch into the current one but a simple
> "git merge <branch>" seems to work well. Is there a difference?

Those manpage sections predate the existance of "git merge <branch>". If you're not planning to use git before November 2006, there's no reason to use the "git pull ." form. They should probably be replaced with more helpful examples at this point.

	-Daniel
*This .sig left intentionally blank*
Previous: Paolo BonziniNext: Brandon Casey
Message 9 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.