{"thread":{"id":"10314","subject":"Problem with git-svnimport","startedAt":"2007-10-16T12:30:30Z","lastAt":"2007-10-18T23:06:46Z","messageCount":3,"participants":["VAUCHER Laurent","Jan Hudec","Steven Grimm"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"56024","messageId":"55DDB08CC9CD2941A70E8D626789A2C906A4031A@ec8l7ljvo9h5dde.hosting.exch","threadId":"10314","inReplyTo":null,"subject":"Problem with git-svnimport","fromName":"VAUCHER Laurent","fromEmail":"vaucher@fermat.eu","sentAt":"2007-10-16T12:30:30Z","receivedAt":"2007-10-16T12:30:30Z","isPatch":false,"sender":{"key":"vaucher@fermat.eu","avatar":null},"body":"  Hi.\n\n  Trying to convert a svn repository to git, I encountered the following\nerror:\n\nUse of uninitialized value in hash element at /usr/bin/git-svnimport\nline 534.\n\n  Line 534 reads:\n\tmy $gitrev = $branches{$srcbranch}{$therev};\n\n  I have installed packages git-core and git-svn on Ubuntu. These\npackage have versions: \"1:1.5.2.5-2-feisty1\"\n\n  The tool seems to choke on tags or branches with special characters\n(underscore, for instance).\n\n\nLaurent.\n"},{"id":"56422","messageId":"20071018180916.GK26127@efreet.light.src","threadId":"10314","inReplyTo":"55DDB08CC9CD2941A70E8D626789A2C906A4031A@ec8l7ljvo9h5dde.hosting.exch","subject":"Re: Problem with git-svnimport","fromName":"Jan Hudec","fromEmail":"bulb@ucw.cz","sentAt":"2007-10-18T18:09:16Z","receivedAt":"2007-10-18T18:09:16Z","isPatch":false,"sender":{"key":"bulb@ucw.cz","avatar":null},"body":"On Tue, Oct 16, 2007 at 14:30:30 +0200, VAUCHER Laurent wrote:\n>   Hi.\n> \n>   Trying to convert a svn repository to git, I encountered the following\n> error:\n> \n> Use of uninitialized value in hash element at /usr/bin/git-svnimport\n> line 534.\n> \n>   Line 534 reads:\n> \tmy $gitrev = $branches{$srcbranch}{$therev};\n> \n>   I have installed packages git-core and git-svn on Ubuntu. These\n> package have versions: \"1:1.5.2.5-2-feisty1\"\n> \n>   The tool seems to choke on tags or branches with special characters\n> (underscore, for instance).\n\ngit-svnimport is obsoleted (or mostly so) by git-svn. Look at that, please.\n\n-- \n\t\t\t\t\t\t Jan 'Bulb' Hudec <bulb@ucw.cz>\n"},{"id":"56442","messageId":"4717E706.5040500@midwinter.com","threadId":"10314","inReplyTo":"20071018180916.GK26127@efreet.light.src","subject":"Re: Problem with git-svnimport","fromName":"Steven Grimm","fromEmail":"koreth@midwinter.com","sentAt":"2007-10-18T23:06:46Z","receivedAt":"2007-10-18T23:06:46Z","isPatch":false,"sender":{"key":"koreth@midwinter.com","avatar":"https://gravatar.com/avatar/71b4d2e8b62f168bdc9e9205341159e3567003b4f9e2127c617c5fa0a1f5bad2?d=mp&s=160"},"body":"Jan Hudec wrote:\n> git-svnimport is obsoleted (or mostly so) by git-svn. Look at that, please.\n>   \n\nThis has been asked before, but I don't think there was a good answer: \nWhat remaining features does git-svnimport have that git-svn doesn't? It \nwould be nice to not have two such tools if one of them doesn't actually \nadd any value. Can we safely deprecate git-svnimport in the next release?\n\n-Steve\n"}]}