From: Alex Riesen <raa.lkml@gmail.com>
To: Ittay Dror <ittay.dror@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: switching upstream tips
Date: Wed, 13 May 2009 11:05:19 +0200 [thread overview]
Message-ID: <81b0412b0905130205u68237834o9172685974cbac4f@mail.gmail.com> (raw)
In-Reply-To: <4A0A858C.2070808@gmail.com>
2009/5/13 Ittay Dror <ittay.dror@gmail.com>:
> Alex Riesen wrote:
>> 2009/5/13 Ittay Dror <ittay.dror@gmail.com>:
>>>
>>> tried git rebase, this is what i get:
>>> git rebase -i upstream master
>>> fatal: Needed a single revision
>>> Invalid base
>>>
>>
>> $ git checkout my-old-master-based-on-old-upstream
>> $ git rebase -i old-upstream
>>
>
> so i need to create an 'old-upstream' branch first, that is based on the tip
> of the old-upstream remote, right? how?
no. Just use the remote reference. Should be something like
origin/master. It is the reference to the commit where to put your
commits on. You can use the SHA1 there, if you wish.
All the rebasing happens on and to that branch of yours
(my-old-master-based-on-old-upstream in the example above)
> (thanks for the patience)
This patience is just about to end. Ever looked at the man pages?
"git help git" can be a good start.
prev parent reply other threads:[~2009-05-13 9:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 6:42 switching upstream tips Ittay Dror
2009-05-13 7:19 ` Alex Riesen
2009-05-13 7:33 ` Ittay Dror
[not found] ` <4A0A777E.7080506@gmail.com>
2009-05-13 7:41 ` Alex Riesen
2009-05-13 7:49 ` Ittay Dror
2009-05-13 7:57 ` Johannes Sixt
2009-05-13 8:07 ` Ittay Dror
2009-05-13 8:16 ` Johannes Sixt
2009-05-13 8:16 ` Alex Riesen
2009-05-13 8:15 ` Alex Riesen
2009-05-13 8:32 ` Ittay Dror
2009-05-13 9:05 ` Alex Riesen [this message]
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=81b0412b0905130205u68237834o9172685974cbac4f@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=ittay.dror@gmail.com \
/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).