On Mar 11, 4:17 pm, Svenn Are Bjerkem <svenn.bjer...@xxxxxxxxxxxxxx> wrote: > Hi, > after performing a > $> git svn clone https://svnserver/svn/a/b/c-T trunk/current -t tags - > b branches > I find that the git master has been tied to one of the branches. It > turns out that the highest svn revision number in the repository was > tied to that branch. [snip] > I guess I could solve the problem by modifying a file in trunk on svn > and commit so that the trunk will get the highest svn revision number > again and redo the clone. I just wanted to confirm this assumption: First I removed the complete git-svn clone and modified a file in trunk and checked it into svn. Then I re-performed the git svn clone as described above. The master in the local git repository is now tied to the trunk of the svn repository. -- Svenn -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
