{"thread":{"id":"27880","subject":"git svn v1 migration, avoid re-clone whole repo","startedAt":"2011-07-21T22:47:27Z","lastAt":"2011-07-23T17:03:51Z","messageCount":2,"participants":["rupert THURNER","Thomas Ferris Nicolaisen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"171826","messageId":"CAJs9aZ-h8J_WYC1cXy9HojwArO8EqWSZnoZ1=LdrqHxeJxz_BQ@mail.gmail.com","threadId":"27880","inReplyTo":null,"subject":"git svn v1 migration, avoid re-clone whole repo","fromName":"rupert THURNER","fromEmail":"rupert.thurner@gmail.com","sentAt":"2011-07-21T22:47:27Z","receivedAt":"2011-07-21T22:47:27Z","isPatch":false,"sender":{"key":"rupert.thurner@gmail.com","avatar":null},"body":"hi,\n\nis there any other means of upgrading to the new svn layout but\ncloning the repository afresh again? the error message i get is:\n\n$ git svn rebase\nMigrating from a git-svn v1 layout...\nData from a previous version of git-svn exists, but\n        .git/svn\n        (required for this version (1.7.5.4) of git-svn) does not exist.\nDone migrating from a git-svn v1 layout\nUnable to determine upstream SVN information from working tree history\n\nrupert\n"},{"id":"171893","messageId":"CAEcj5uXUbJGj0Gjji-dRcsQuoQ3kP-LXcXGjtwFiZLFP5c-R6g@mail.gmail.com","threadId":"27880","inReplyTo":"CAJs9aZ-h8J_WYC1cXy9HojwArO8EqWSZnoZ1=LdrqHxeJxz_BQ@mail.gmail.com","subject":"Re: git svn v1 migration, avoid re-clone whole repo","fromName":"Thomas Ferris Nicolaisen","fromEmail":"tfnico@gmail.com","sentAt":"2011-07-23T17:03:51Z","receivedAt":"2011-07-23T17:03:51Z","isPatch":false,"sender":{"key":"tfnico@gmail.com","avatar":"https://gravatar.com/avatar/628cf28a25ca4c596c7284562100f70f0ef908bcbfadd4da1eb3d48c23658d01?d=mp&s=160"},"body":"Hi Rupert,\n\n> is there any other means of upgrading to the new svn layout but\n> cloning the repository afresh again? the error message i get is:\n>\n> $ git svn rebase\n> Migrating from a git-svn v1 layout...\n> Data from a previous version of git-svn exists, but\n>        .git/svn\n>        (required for this version (1.7.5.4) of git-svn) does not exist.\n> Done migrating from a git-svn v1 layout\n> Unable to determine upstream SVN information from working tree history\n>\n\nCan you say in more concrete steps how you created the repository\nwhere this happens?\n\nI've seen this error message in repositories that are clones of\ngit-svn repositories. They are \"simple\" git repositories with no link\nestablished to the SVN repository (no notion of svn in the\n.git/config). If this is the case, read on:\n\nI usually fix this by initializing git svn in the repo:\n\n> git svn init [same params as the initial git svn clone] [svn url]\n\nAnd then you have to update the latest git-svn ref to point at the\nlast git-svn commit. Usually this goes something like:\n\n> git update-ref refs/remotes/git-svn refs/remotes/origin/master\n\n... assuming that the git-svn repo you cloned from is a remote repo\nwith the name \"origin\".\n\nNote that in a git svn clone with branches the above git-svn reference\nwill be probably be branch name instead.\n\nHope this helps,\n\n-Thomas\n"}]}