git - Different hash in the same commits after svn synchronization -


so i've got big svn repo , did migration git , got correct repo

git svn clone path_to_svn 

after did synchronization

git svn fetch git svn rebase 

and worked first time, on second attempt failed unable determine upstream svn information working tree history, though on sync branch, wasn't changed @ all, sync on , merge master it. decided new clone , try set remotes on project , merge new branch , after cloning spotted same commits have different hash, i'm 100% sure, same. same diffs, authors , on.

why see different hash same commits?

usually, git-svn create same git objects when clone repository again. use subversion repository’s author name , checkin date set commit author , committer, set commit message according checkin message in subversion, , create content correctly. should end identical commit objects (i verified case myself).

however, applies, if conditions same both clones. means example specify same branch layout, , server returns proper timestamps (i see issue dst changes). it’s important subversion url still identical since it’s being embedded in git commit messages.

i’d suggest git cat-file -p <hash> of 2 commits should identical in each clone. way, can try figure out might difference between clones. open gitk side-by-side each repository go through commits , try spot 1 history might have changed.


Comments

Popular posts from this blog

jquery - How do you format the date used in the popover widget title of FullCalendar? -

asp.net mvc - SSO between MVCForum and Umbraco7 -

Python Tkinter keyboard using bind -