------------------------------ On Sat, Oct 25, 2014 06:32 BST Eric Wong wrote:
Show 10 quoted lines
>Hin-Tak Leung <htl10@users.sourceforge.net> wrote: >> the old didn't missing a revision - just a revision 'message' - blank >> instead of 3 words, above the git svn id. I supppse it is possible >> some power problem or etc caused this. I'll check the other branches >> as well, and possibly clone again to be sure. ( The new clone did have >> one break...) > >Oh, there's a possibility the commit message in SVN was edited/added >after-the-fact, but that depends on the SVN admin (most never allow >or do it).
That's a possibility - the old clone was created by fetching every few days. It is possible that the author edited it after commiting a blank message and i fetched.
btw, git svn seems to disallow single word commit messages (or is it a svn config?). i found that i could not do git svn dcommit, when i had merely did git commit -m 'typos', for example, for an svn repo i have write access to. (I don't have them many such things, so it is difficult to tell whether it is a repo config, or a git svn strangeness). i just do rebase and do 'typo correction' or something before re-dcommit in the past.