Re: git-svn performance

Hin-Tak Leung· Oct 25, 2014, 05:23 UTC · lore

------------------------------ On Sat, Oct 25, 2014 01:02 BST Eric Wong wrote:

Show 11 quoted lines

>Hin-Tak Leung <htl10@users.sourceforge.net> wrote:
>> Comparing trunk of old and new, I see one difference -  One short
>> commit message is missing in the *old* (the "Add checkPoFiles etc." part)
>> and so all the sha1 afterwards differed. Is that an old bug that's fixed
>> and therefore I should throw away the old clone? 
>
>I don't recall a bug which would cause a revision to be skipped.
>I suppose it's alright now the new clone has that revision.
>Perhaps there was a power outage or improper shutdown?
>
>At least we can be glad current versions see this revision...

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...)

Eric Wong· Oct 25, 2014, 05:32 UTC · re: Hin-Tak Leung · lore

Hin-Tak Leung <htl10@users.sourceforge.net> wrote:

Show 5 quoted lines

> 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).