{"thread":{"id":"14230","subject":"how does git svn work","startedAt":"2008-06-30T19:57:32Z","lastAt":"2008-06-30T20:57:07Z","messageCount":2,"participants":["Thomas Koch","Brian Gernhardt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"81774","messageId":"200806302157.32828.thomas@koch.ro","threadId":"14230","inReplyTo":null,"subject":"how does git svn work","fromName":"Thomas Koch","fromEmail":"thomas@koch.ro","sentAt":"2008-06-30T19:57:32Z","receivedAt":"2008-06-30T19:57:32Z","isPatch":false,"sender":{"key":"thomas@koch.ro","avatar":null},"body":"Hi,\n\nis there a document explaining the internals of GIT-SVN? I'd like to\nknow, which SVN commands are executed in the background and how git-svn\nrecognizes branch creation in SVN.\n\nIn particular I want to follow the repository at:\nhttp://pubsvn.ez.no/nextgen/\n\nThe layout is like\n/trunk\n/stable\n  |- 4.0\n  |- 3.9\n  |- 3.8\n  ...\n/releases\n  |- 4.0\n  |- 4.0r1\n  |- 3.9\n  |- 3.9r1\n  |- 3.9r2\n\n\nI do not know, whether git-svn can create branches automatically for\neach directory under /stable and one main branch for trunk or whether I\nneed to create one svn-remote definition for every svn directory I want\nto track.\n\n\nBest regards,\n-- \nThomas Koch, Software Developer\nhttp://www.koch.ro\n\nYoung Media Concepts GmbH\nSonnenstr. 4\nCH-8280 Kreuzlingen\nSwitzerland\n\nTel    +41 (0)71 / 508 24 86\nFax    +41 (0)71 / 560 53 89\nMobile +49 (0)170 / 753 89 16\nWeb    www.ymc.ch\n-- \nThomas Koch, Software Developer\nhttp://www.koch.ro\n\nYoung Media Concepts GmbH\nSonnenstr. 4\nCH-8280 Kreuzlingen\nSwitzerland\n\nTel    +41 (0)71 / 508 24 86\nFax    +41 (0)71 / 560 53 89\nMobile +49 (0)170 / 753 89 16\nWeb    www.ymc.ch\n"},{"id":"81776","messageId":"02EDA057-6DE9-4038-ACDA-8763BE0A0D0C@silverinsanity.com","threadId":"14230","inReplyTo":"200806302157.32828.thomas@koch.ro","subject":"Re: how does git svn work","fromName":"Brian Gernhardt","fromEmail":"benji@silverinsanity.com","sentAt":"2008-06-30T20:57:07Z","receivedAt":"2008-06-30T20:57:07Z","isPatch":false,"sender":{"key":"benji@silverinsanity.com","avatar":"https://gravatar.com/avatar/e06c101dbc25c68114d859b4a9ec7cf8a2c52fd2b0270ef0eac0e2e63ff22311?d=mp&s=160"},"body":"\nOn Jun 30, 2008, at 3:57 PM, Thomas Koch wrote:\n\n> In particular I want to follow the repository at:\n> http://pubsvn.ez.no/nextgen/\n>\n> The layout is like\n> /trunk\n> /stable\n>  |- 4.0\n>  |- 3.9\n>  |- 3.8\n>  ...\n> /releases\n>  |- 4.0\n>  |- 4.0r1\n>  |- 3.9\n>  |- 3.9r1\n>  |- 3.9r2\n>\n>\n> I do not know, whether git-svn can create branches automatically for\n> each directory under /stable and one main branch for trunk or  \n> whether I\n> need to create one svn-remote definition for every svn directory I  \n> want\n> to track.\n\nI'm not sure what commands git-svn uses, but it looks like the  \nfollowing command should work:\n\ngit svn clone --trunk=trunk --tags=releases --branches=stable http://pubsvn.ez.no/nextgen/ \n  nextgen\n\nThat should create a nextgen git repository with a master branch  \nfollowing SVN stable, and automatically grabbing anything under stable  \nor releases as a new branch.  (I actually marked releases as a tag but  \nI think git-svn treats them as branches, since they can change on the  \nSVN side.)\n\n~~ Brian\n"}]}