Hi, thanks for your reply. I have a few final comments on this matter.
I think that you and SVN have the correct idea, that when you run 'svn log file:///tmp/test/svn_repo/trunk', then you are asking for the history of the trunk sub-directory, which didn't exist (in my previous example) more than 2 revisions ago. I think it comes down to me trying to do a few complicated things during my import: 1) Track only the history of the 'trunk' directory (I don't want directories called tags and branches in a git repo) - ie something like this: svn log file:///tmp/test/svn_repo/trunk/* 2) Track the entire history of files, even before they were moved to 'trunk' - Hard to do if you only get the history of a single directory 3) There wasn't always a tidy 'trunk'/'branches'/'tags' sub-division - Which rules out using git-svnimport, which needs the above layout. 4) Sometimes the entire project sub-directory in svn changed (eg: projects/old_project renamed to projects/new_project somewhere in the past) - This rules out importing the entire project directory (including trunk,branches,tags) with git-svn, since it (probably?) won't retrieve history from projects/old_project. I agree that the above requirements are very hard for an importer to follow sanely in all cases :-) So, in cases like the above I will continue to manually fix up history with a series of 'git-svn init' and 'git-svn fetch' commands (with revision ranges and svn paths) during my initial import. Perhaps I can forward a HOWTO I put together for doing the above? Then users can refer to it when they have 'svn log'-unfriendly histories like mine, but want to get the entire (relevant) history into git regardless. Regards, David. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
