esskov@xxxxxxxxxx wrote: > Hi, > > I'm trying to clone the trunk of an svn repo, so that I can work on a set > of patches locally, and then occasionally push some of them back to svn. > > The git-svn clone seems to go well, and the resulting git log looks > alright. However, git-svn info and git-svn rebase both say "Unable to > determine upstream SVN information from working tree history". > Also, git-svn log shows nothing. I'm using the svn:// protocol btw, but I > guess the protocol shouldn't matter? Protocol shouldn't matter. Do you have any non-linear history from merges in git? git-svn (and SVN) doesn't play very nicely with non-linear history that git merges can generate. Does having a clean clone of that repo fix things? You didn't use --no-metadata or blow away your .git/svn/* directories, did you? > To test if this was a general problem, I just tried to git-svn clone a > repo on some public svn server which was also using the svn protocol. I > used exactly the same syntax for the svn init and fetch commands. However, > the resulting git repo did NOT suffer from the problem, i.e., git-svn info > reported nicely etc. > > At some point I suspected that there might be a problem with the > "git-svn-id ..." lines in the commits for the problematic repo, but they > look just like the ones for the working repo. The .git/config files of the > working and the non-working git-repos are similar as well. > > What could be causing this problem? Which version of git svn is this? Are there any weird characters in the URL? Off the top of my head I can't think of anything else; I assume you're not allowed to share access to the repo (or to the clone) you're having problems with? -- Eric Wong -- 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