On Fri, Nov 21, 2008 at 02:30, paulfred <paul.fredrickson@xxxxxxxxx> wrote: > $ git svn dcommit > Unable to determine upstream SVN information from HEAD history. > Perhaps the repository is empty. at /usr/local/libexec/git-core/git-svn line 435. > > So apparently my problem is NOT the empty commit at all, but trying to use > noMetadata. I am surprised that it fails on a fresh download though. Is there > something I might have done while hacking that would cause git-svn to lose > track of trunk again? Is my only option to convince everyone to ignore > the "noise" in my comments? Uhm, as I understand it, git svn needs that metadata to dcommit, unless the .git/svn/git-svn/.rev_db is intact. The --no-metadata switch should be used only when you're doing a one-time import of a svn repo. During my usage of git svn, it removed the git-svn-id tags from the commit message when you 'git svn dcommit', so I don't understand why you need to use --no-metadata in the frist place. -- Cheers, Sverre Rabbelier -- 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
