On Thu, Feb 24, 2011 at 1:27 AM, Hin-Tak Leung <hintak.leung@xxxxxxxxx> wrote: ... > After I fixed that and continue as I intended, then there is another > bomb-out, when git-svn complains about a git commit message of mine > (with minor edit): > ------------- > Running > perl -pi -e 's(sometag="original")(sometag="replacement")' directory/* > ------------- > being empty. On hind-sight, it is probably not a good idea to have > perl regular expression code within a commit message (git-svn itself > being in perl), but complaining about a non-empty commit message (and > seem to be a valid one, no strange utf8/chinese characters, etc) being > empty seems to be a bug. Just adding to this part: it appears that git-svn doesn't like the first-line of the commit message being just one word (in this case, "Running"). I have just done one where the commit message was a single word "renaming" (it would be obvious which file I was renaming, so I thought there is no need to say more), which also caused git-svn dcommit to complain about it being empty. Many thanks for git-svn - as I wrote below, I wouldn't use anything else these days. > Hope this helps. BTW, git-svn is a great tool, and thanks a lot for > that - I wouldn't use anything else (including the "authentic" svn > client) to interact with svn repositories these days. > > Hin-Tak > -- 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