git/list[1] front-page[2] threads[3] people[4] search[5] about
 

switching upstream tips

From
Ittay Dror <ittay.dror@gmail.com>
Date
May 13, 2009, 06:42 UTC
Message-ID
<4A0A6BD1.7050907@gmail.com>
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: Alex Riesen
Message 1 of 12 in “switching upstream tips”
  1. Ittay DrorMay 13, 2009
  2. Alex RiesenMay 13, 2009
  3. Ittay DrorMay 13, 2009
  4. Alex RiesenMay 13, 2009
  5. Ittay DrorMay 13, 2009
  6. Johannes SixtMay 13, 2009
  7. Ittay DrorMay 13, 2009
  8. Johannes SixtMay 13, 2009
  9. Alex RiesenMay 13, 2009
  10. Alex RiesenMay 13, 2009
  11. Ittay DrorMay 13, 2009
  12. Alex RiesenMay 13, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.