{"thread":{"id":"33478","subject":"git-svn: wrong history after cloning a repository","startedAt":"2013-04-11T17:04:23Z","lastAt":"2013-04-11T17:04:23Z","messageCount":1,"participants":["Frans Fürst"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"213973","messageId":"1365699863.30393.30.camel@blackbox.scitics","threadId":"33478","inReplyTo":null,"subject":"git-svn: wrong history after cloning a repository","fromName":"Frans Fürst","fromEmail":"frans.fuerst@scitics.de","sentAt":"2013-04-11T17:04:23Z","receivedAt":"2013-04-11T17:04:23Z","isPatch":false,"sender":{"key":"frans.fuerst@scitics.de","avatar":null},"body":"Hi,\n\nI'm currently struggeling with a strage behaviour of git-svn: After\ngit-svn-cloning a given repository (see attachment) in some cases the\ngit blame differs from the svn blame. The history looks like after a\nmerge all affected files have been added from scratch at this revision.\n\nThe behaviour can be observed using at least the following versions of\ngit:\n1.7.10.2\n1.8.1.4\n1.8.2.GIT\n\nGiven: * svn-repository, svn-server 1.6.11, apache2 module via WEB DAV\n       * repository like the one attached:\n            * standard svn layout\n            * branch ^/branches/feature1 copied from ^/trunk\n            * changes made and files added on \n              project1/branches/feature1 by 'testuser1'\n            * branch ^/branches/rc-1.0 copied from ^/trunk on \n              revX by 'mergeuser'\n            * ^/branches/feature1 merged to ^/trunk on \n              revY by 'mergeuser'\n            * ^/branches/rc-1.0 merged back to trunk revZ by 'mergeuser'\n\nAction: git svn clone -s <repo-url>\n        git blame <some_file_modified_on-feature1>\n\nObserved behaviour: Changes being made on project1/branches/feature1\nbeing associated to 'mergeuser' who integrated feature1 but not\nimplemented on that branch.\n\n> $ git blame src/file2.txt\n> 9846ece6 (mergeuser 2013-04-11 14:31:21 +0000 1) content2-1\n> 9846ece6 (mergeuser 2013-04-11 14:31:21 +0000 2) content2-2\n> 9846ece6 (mergeuser 2013-04-11 14:31:21 +0000 3) content2-3\n\nAction: svn blame <repo-url>/trunk/<some_file_modified_on-feature1>\n\nObserved behaviour: Changes are correctly associated to user1\n\n> $ svn blame src/file2.txt\n>     4  testuser1 content2-1\n>     4  testuser1 content2-2\n>     4  testuser1 content2-3\n\nI don't know yet which steps are really needed to re-create a repository\nwith this behaviour. My guess is that adding files together with a merge\n(see r6 in the attached repository) has something to do with it.\n\nCan you tell me whether this is a known issue or if there's a work\naround for this? Unfortunately I'm not very into perl so I can't solve\nthis on my own. Please let me know if you need additional information.\n\nThanks\n\nFrans\n"}]}