git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar" <aneesh.kumar@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Junio C Hamano" <junkio@cox.net>, git@vger.kernel.org
Subject: Re: git pull and merging.
Date: Wed, 6 Dec 2006 15:35:15 +0530	[thread overview]
Message-ID: <cc723f590612060205p1fd26cd7u3c7efc723b0177de@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0612061019350.28348@wbgn013.biozentrum.uni-wuerzburg.de>

On 12/6/06, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>
> > I almost felt the branch.<name>.merge was for that.
>
> No. This tells git which _default_ branch to merge with. I.e.
>
> $ git repo-config branch.master.remote origin
> $ git repo-config branch.master.merge next
>
> means that if your current branch is "master", a "git pull" _without_
> parameters will default to the branch "next" of the remote "origin" you
> just set up like above.

This doesn't work. So this is what i tried
test repository with master and devel branch
cloned it to test.devel

.git/config have

[branch "devel"]
        remote = origin
        merge = devel

Now IIUC this should be when i am in branch devel when i do a git pull
pull from origin remote and merge with the local branch devel  the
remote branch devel.

But git pull says already up to date.

Now i thought merge should be local reference. So i changed it to
merge = remotes/origin/devel.

That also didn't work.

Then i tried the name of the branch should be indicated as
"refs/heads/devel" . That also didn't work.

So i guess i am missing something.


  parent reply	other threads:[~2006-12-06 10:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06  4:51 git pull and merging Aneesh Kumar
2006-12-06  5:02 ` Junio C Hamano
2006-12-06  5:21   ` Aneesh Kumar
2006-12-06  9:26     ` Johannes Schindelin
2006-12-06 10:00       ` Peter Baumann
2006-12-06 10:14         ` Johannes Schindelin
2006-12-06 10:23           ` Peter Baumann
2006-12-06 10:05       ` Aneesh Kumar [this message]
2006-12-06 10:28         ` Jakub Narebski
     [not found]           ` <cc723f590612060236k7839942el8d048eedfdee3682@mail.gmail.com>
     [not found]             ` <cc723f590612060248y6f730a54l3a2aadfa6500d36d@mail.gmail.com>
2006-12-06 10:48               ` Fwd: " Aneesh Kumar
2006-12-06 16:44         ` Josef Weidendorfer
2006-12-07  6:46           ` Aneesh Kumar K.V
2006-12-07 11:27             ` Josef Weidendorfer
2006-12-07 19:06               ` Junio C Hamano
2006-12-07 22:54                 ` Josef Weidendorfer
2006-12-08  1:56                   ` Santi Béjar
2006-12-08 17:23                     ` Josef Weidendorfer
2006-12-08 19:12                       ` [PATCH] Add branch.*.localmerge and documentation update Josef Weidendorfer
2006-12-08 20:52                         ` Santi Béjar
2006-12-08 21:38                           ` Junio C Hamano
2006-12-08 21:48                             ` Jakub Narebski
2006-12-08 22:01                             ` Josef Weidendorfer
2006-12-08 22:34                               ` Junio C Hamano
2006-12-08 23:17                                 ` Josef Weidendorfer
2006-12-08 23:41                                   ` Junio C Hamano
2006-12-09  1:28                                     ` [PATCH] Add branch.*.merge warning " Josef Weidendorfer
2006-12-09 16:14                                       ` Santi Béjar
2006-12-08 21:39                           ` [PATCH] Add branch.*.localmerge " Josef Weidendorfer
2006-12-08 22:15                             ` Santi Béjar
2006-12-08 20:09                       ` git pull and merging Santi Béjar
2006-12-08  7:07                   ` Junio C Hamano
2006-12-07 23:06                 ` Junio C Hamano
2006-12-08  2:04                   ` Santi Béjar
2006-12-08 11:48               ` Jakub Narebski
2006-12-06  9:31     ` Jakub Narebski
2006-12-06  9:58       ` Johannes Schindelin

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=cc723f590612060205p1fd26cd7u3c7efc723b0177de@mail.gmail.com \
    --to=aneesh.kumar@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).