I am using git-svn version 1.5.3.rc1.4.gaf83 (svn 1.4.3), and I work with an SVN repository that is layed out like this: /trunk/proj1/ ... /trunk/proj2/ ... /trunk/testing/ ... /branches/proj1/ ... /branches/proj2/ ... /branches/testing/ /branches/testing/0000-baseline /tags/proj1/ ... /tags/proj2/ ... /tags/testing/ /tags/testing/0000-baseline-0 I want to track the testing project, so I tried to use this git-svn command line: git-svn clone <base-url> -T/trunk/testing -t/tags/testing -b/branches/testing testing This appears to work, though I do get this warning message (edited for privacy): W: Ignoring error from SVN, path probably does not exist: (175002): RA layer request failed: REPORT request failed on '/<server_path>/!svn/bc/101': REPORT of '/<server_path>!svn/bc/101': Could not read chunk size: Secure connection truncated (https://<myserver>) When I run 'git branch -a' in the new testing directory I get this: * master 0000-baseline 0000-baseline@1546 1.0 1.0@1549 1.0@1656 tags/0000-baseline tags/0000-baseline-0 tags/0000-baseline@1663 Where is the remote branch for trunk? And, why do I have remote entries for the defunct 1.0 branch that I deleted from svn earlier today? What's more, the latest changes from /trunk/testing do not appear in my working directory, and gitk confirms that master is pointing at the same commit as tags/0000-baseline-0. If I just try to track the trunk like this: git-svn clone <base-url>/trunk/testing Then I get all of the latest changes and 'git branch -a' shows: * master git-svn So that seems OK at least. It just doesn't work when I try to get branches and tags. For now, I'll just work this way. FWIW, I suspect this behavior may be related to recent changes I made to the Subversion repository. I created /branches/testing/0000-baseline today by copying an _old_ revision of /trunk/testing. Then I created /tags/testing/0000-baseline-0 by copying /branches/testing/0000-baseline. No commits have been done on /testing/trunk since then. Perhaps the recent (probably latest) commit that copied an OLD version of trunk is somehow confusing git-svn? Once I commit a change to the subversion trunk, I'll try to clone trunk, branches, and tags again and post an update to this message. Maybe it will work then. Thanks for your help. Bradford C. Smith - 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
