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 11, 2008, 01:13 UTC
Message-ID
<484F26C9.9080608@keyaccess.nl>
In-Reply-To
<ee77f5c20806101806u6dc04152rb8307eb12a6167c@mail.gmail.com>
On 11-06-08 03:06, David Symonds wrote:
Show 8 quoted lines
> On Wed, Jun 11, 2008 at 10:51 AM, Rene Herman <rene.herman@keyaccess.nl> wrote:
> 
>> 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?
> 
> git pull also does a fetch in it's usual mode of operation, and runs
> git merge to do merge changes in the remote-tracking branches.

So in the case of merging a branch from the local repository into the current branch, there is no difference between the two?

Rene.
Previous: David SymondsNext: Miklos Vajna
Message 3 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.