Eric Wong wrote: [SNIP] > > Using -q suppresses potentially useful information. I wouldn't use > it if you're not sure about what you're doing. OK. > > I would do something like this: > > ... (same stuff as above before with svn setup...) > git clone $ORG_REPO $GIT_REPO > cd $GIT_REPO > git-svn init "$REPO"/trunk > git-svn fetch > > # sync the SVN repo with initial-uboot > # this will just commit a snapshot, without history, which I assume > # is what you want. > git-branch initial-uboot f5e0d03970409feb3c77ab0107d5dece6b7d45c9 > git-svn commit initial-uboot > git checkout -b svn-branch remotes/git-svn > git-pull . tmcu2 > > # this should work assuming the path from initial-uboot..tmcu2 is linear > # use gitk initial-uboot..tmcu2 to check > git-svn dcommit Great! This was exactly what I wanted, thanks. I never realized that one should do git-svn commit initial-uboot to get that single commit. I also replaced git-svn dcommit with git-svn commit remotes/git-svn..svn-branch as I don't have that version yet. You should add this as an example I think. Can I ask for an example that used multi-init and multi-fetch? I tried, but could not make it work. > > Also, git-svn is really designed for individual developers who prefer to > use git, but need to interact with project that already uses SVN. > u-boot already uses git, so I don't see why you'd need git-svn :) Yes, but the thing is that the rest of our product is svn based including the build env. So I have to supply a SVN tree for build purposes and if someone else has to do a minor fix I can't ask him to learn git first :( jcoke - 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