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

Fwd: git+svn - repo upgrade from 1.6.6.4 to 1.7.1 fails

From
FFred <fred@akafred.com>
Date
May 31, 2010, 11:09 UTC
Message-ID
<AANLkTikYYjl6Gv8SRMvtmzW1pyzkyu_mwLyEGHdWuH00@mail.gmail.com>
In-Reply-To
<AANLkTin-k5zIDZysiLbTusqDwqxGWDxxAOPljLuRlIMD@mail.gmail.com>

Hi, I have a project with two remotes - one git and one svn. One branch is only used for "git svn rebase", and then I cherrypick or merge from it into my master branch. Most work is done in the master branch (or other topic branches only available in git)

The repo was created under git 1.6.6.4. After updating git a while back (to 1.7.1) it was time to merge inn a few things from svn - so i switched to my "subversion" branch and did a

$ git svn rebase

Migrating from a git-svn v1 layout... Data from a previous version of git-svn exists, but .git/svn (required for this version (1.7.1) of git-svn) does not exist. Done migrating from a git-svn v1 layout Unable to determine upstream SVN information from working tree history --- I read this as: "I see your repo has some svn stuff and that it is backlevel. I'll fix it for you. Oh shit, now I can't determine what svn revision you are on."

Any ideas on how to resolve this? We're a dozen developers relying on this so it would be nice find a way with minimal impact to the users...

For now I'll do the rebasing in a back-level git client...
- Fred
Next: Fred
Message 1 of 2 in “Fwd: git+svn - repo upgrade from 1.6.6.4 to 1.7.1 fails”
  1. FredMay 31, 2010
  2. FredMay 31, 2010

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.