From: Ittay Dror <ittay.dror@gmail.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: switching upstream tips
Date: Wed, 13 May 2009 11:32:12 +0300 [thread overview]
Message-ID: <4A0A858C.2070808@gmail.com> (raw)
In-Reply-To: <81b0412b0905130115v78b5065bjdeb3f349072eed4c@mail.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? (thanks for the patience)
>
>>> Ok, that simplifies everything. Just cherry-pick (see "git cherry-pick")
>>> your commits on new upstream. You might find it easiest if you cherry-pick
>>> them on commits in new upstream which correspond the old-upstream
>>> exactly.
>>>
>> can you explain a bit more how to work with git cherry-pick? if i understand
>> correctly, i need to write down my commits, switch to the new upstream tip
>> ('git checkout upstream master'?) and then call git cherry-pick for each of
>> my commits.
>>
>
> $ gitk old-upstream-with-my-changes-on-top &
> $ git checkout -b my-new-master-on-top-of-new-upstream new-upstream
> ...select a commit in gitk...
> $ git cherry-pick <paste-the-selected-commit-here> # hit Enter
>
> repeat until you run out of commits you want to have on top of the new upstream.
>
next prev parent reply other threads:[~2009-05-13 8:32 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 [this message]
2009-05-13 9:05 ` Alex Riesen
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=4A0A858C.2070808@gmail.com \
--to=ittay.dror@gmail.com \
--cc=git@vger.kernel.org \
--cc=raa.lkml@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.