Complex rebasing

Stepan stepan.sindelar at
Fri Dec 9 16:08:17 UTC 2016

On 09/12/16 16:31, Andrew Haley wrote:
> On 08/12/16 18:47, Tom Rodriguez wrote:
>>> On Dec 8, 2016, at 10:39 AM, Andrew Haley <aph at> wrote:
>>> On 08/12/16 18:29, Tom Rodriguez wrote:
>>>> git pull —rebase origin master is the usual command I use
>>> Ah, OK.  That is very different from what I did.
>>> I tried "git rebase" but it rebased my checked-out code from my
>>> personal master, not graalvm's real master.
>>> My remote origin is
>>> (branch aarch64_graal_misc_fixes)
>>> and I want to rebase from
>>> (branch master)
>> Right, so in my example origin would be replaced with whatever you named the remote for graalvm/graal-core.
>> One problem with git is that there are usually 12 ways to do the same thing which complicates giving instructions to someone on how to solve a problem.  Having multiple remotes makes it more complicated as well.  If you have your own repo you might never use master which can get out of date with upstream.  My personal practice is that origin always refers to the repo I will end up pushing to and my personal repo is named after my GitHub user name.
> It's still not working for me.
> mercury:graal-core $ git remote add graal-master ssh://
> mercury:graal-core $ git remote -v
> graal-master	ssh:// (fetch)
> graal-master	ssh:// (push)
> graal-origin	ssh:// (fetch)
> graal-origin	ssh:// (push)
> origin (fetch)
> origin (push)
> mercury:graal-core $ git pull --rebase origin graal-master
> fatal: Couldn't find remote ref graal-master

I believe it should be 'git pull --rebase graal-origin master' -- first 
the remote name and then the name of the branch you want to pull from 
that remote.


More information about the graal-dev mailing list