On Sep 8, 2010, at 6:36 PM, Daniel Trebbien wrote: >> Or you can downloading both trunk and nano as separate branches. I think it fetches each revision twice, but it will prevent it from downloading the entire history for each subdirectory branch. >> >> fetch = trunk:refs/remotes/trunk >> + fetch = trunk/nano:refs/remotes/nano >> >> This will make your history look a little odd since trunk will have every commit that nano does but be a completely separate branch. (It also seems to confuse `git-svn find-rev`.) > Looking through the Nano repository, it appears that early tags were > copies of the entire trunk, but later tags (`nano_2_0_8` and onward) > were copies of just `trunk/nano`. > > Is there a way that I can inform git-svn that tags `nano_2_0_8`, > `nano_2_0_9`, ... should all be based off of `remotes/trunk/nano`? git-svn will automatically determine that it's branched off of trunk/nano, but will only save the commits for trunk/nano if you create a branch for it. That's I think adding a fetch line for trunk/nano as the lesser of two evils. ~~ Brian -- 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