git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Miklos Vajna <vmiklos@frugalware.org>,
	David Symonds <dsymonds@gmail.com>, git <git@vger.kernel.org>
Subject: Re: "git pull . <branch>" versus "git merge <branch>"
Date: Wed, 11 Jun 2008 04:09:45 +0200	[thread overview]
Message-ID: <484F33E9.1060205@keyaccess.nl> (raw)
In-Reply-To: <484F32B1.4050506@gnu.org>

On 11-06-08 04:04, Paolo Bonzini wrote:
> Miklos Vajna wrote:
>> On Wed, Jun 11, 2008 at 03:13:45AM +0200, Rene Herman 
>> <rene.herman@keyaccess.nl> wrote:
>>> So in the case of merging a branch from the local repository into the 
>>> current branch, there is no difference between the two?
>>
>> There is no difference, but you really want to use git merge and not git
>> pull in such a case, I guess the git pull form is supported mainly to
>> keep backwards compatibility.
> 
> However, when you're on a tracking merge

On a what? :)

> only "git pull" will merge the right branch automatically into the
> current branch, fetching the branch name to merge from the config.
> If the branch.*.remote config key is ".", it will do a local merge.
> 
> Note that "git pull ." is optimized in that the fetch does nothing 
> except setting up MERGE_HEAD.

Rene.

  reply	other threads:[~2008-06-11  2:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11  0:51 "git pull . <branch>" versus "git merge <branch>" Rene Herman
2008-06-11  1:06 ` David Symonds
2008-06-11  1:13   ` Rene Herman
2008-06-11  1:56     ` Miklos Vajna
2008-06-11  2:01       ` Rene Herman
2008-06-11  2:04       ` Paolo Bonzini
2008-06-11  2:09         ` Rene Herman [this message]
2008-06-11  5:23           ` Paolo Bonzini
2008-06-11 17:56 ` Daniel Barkalow
2008-06-11 18:32   ` Brandon Casey
2008-06-11 19:46     ` Daniel Barkalow
2008-06-11 21:01       ` Brandon Casey
2008-06-11 21:49         ` Mikael Magnusson
2008-06-12  0:56           ` Rene Herman
2008-06-11 23:01 ` Junio C Hamano
2008-06-12  1:00   ` Rene Herman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=484F33E9.1060205@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=bonzini@gnu.org \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=vmiklos@frugalware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).