Re: [SVN-MIGRATION] Steps for the SVN migration

On Jul 26, 2008, at 5:01 PM, Lars Strojny wrote:

Hello, Am Samstag, den 26.07.2008, 15:24 -0700 schrieb shire: [...]

While I think we shouldn't limit our freedom too much here (I like the idea of thinking outside the box), structures like the above will cause a lot of grief if we ever want to move to another revision control system that won't recognize the above setup correctly. It'll also make a lot of headaches for developers wanting to import into decentralized systems like git etc (just verified this won't work with the current git-svn, unless someone knows a way to do this easily).

Right, but I don't think it supports the multiple subdirectory structure that was proposed. ie: --stdlayout specifies these paths as /branches and /tags and the --branches and --tags let you set these to some other path, but I don't believe you can specify multiple branch and tag paths, nor will it follow subdirectories correctly as it can't logically determine the correct structure. ie: "--branches=branches/private --branches=branches/releases" would result in one overwriting the previous, let me know if I'm missing something but I assume this would cause problems for other import tools as well. This could of course be fixed by adding more complicated configurations to the import/conversion tools, this should be taken into consideration with the benefits we get from this more complicated directory structure. -shire