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

Dealing with rewritten upstream

From
Jay Soffian <jaysoffian@gmail.com>
Date
Sep 30, 2011, 22:09 UTC
Message-ID
<CAG+J_DwR4vE6iYt475EM7-VDNi4hG3jhdmXWSbJ04Y9fyHeuLw@mail.gmail.com>

I have a repo w/over two years of history whose upstream repo is a git-svn mirror.

The upstream folks recently announced they need to retire the existing repo and replace it with a new repo. The new repo is identical to the old repo tree wise (commit for commit), but some of the commits in the old repo had incorrect authorship which is corrected in the new repo, so the new repo has different commit IDs than the old.

(i.e., it's as if they've run filter-branch --env-filter on the old repo.)
My repo has many merge points with the old history.
Pictorially:
---A---B---C---D---E... new-upstream/master
---a---b---c---d---e... old-upstream/master
    \       \       \
     1---2---3---4---5  master
The obvious way do deal with this situation is:
$ git merge -s ours -m "Splice in new-upstream/master" E
Are there any other/better options I'm missing?

(Eventually upstream plans to migrate entirely to git, so I can't just run git-svn myself.)

j.
Next: Michael Witten
Message 1 of 4 in “Dealing with rewritten upstream”
  1. Jay SoffianSep 30, 2011
  2. Michael WittenSep 30, 2011
  3. Jay SoffianSep 30, 2011
  4. Philip OakleyOct 1, 2011

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.