From: Ittay Dror <ittay.dror@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: switching upstream tips
Date: Wed, 13 May 2009 09:42:25 +0300 [thread overview]
Message-ID: <4A0A6BD1.7050907@gmail.com> (raw)
Hi,
I'm working on a repository in github that is forked from another
repository. I've committed several times and pulled (merged) from the
upstream a few times (so the committs are interleaved). The upstream
repository is a clone of an SVN repository (in apache). The project has
switched svn repositories (moved from incubation to top level project)
and so created a new repository in github.
Now I want to start working with the new upstream repository. My problem
is that because of the changes in the backing SVN, the objects are
completely new, so when i try 'git pull new-upstream master', I get a
lot of add/add conflicts. Most of the conflicts show the whole file has
changed while actually just a few lines differ. So I'm having trouble
making sense of the mess.
What I'm trying to figure out is how to do the following:
* Reorder my history so that my commits are on top of the tip of the old
upstream repository.
* Change the upstream repository reference so it points to the new
repository
* Apply my commits on top of the new upstream repository
Of course any other alternative which will allow me to continue to work
with the new upstream is also welcome.
Thank you,
Ittay
next reply other threads:[~2009-05-13 6:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 6:42 Ittay Dror [this message]
2009-05-13 7:19 ` switching upstream tips 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
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=4A0A6BD1.7050907@gmail.com \
--to=ittay.dror@gmail.com \
--cc=git@vger.kernel.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 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.