I found that the hashcode of the same commit is different before and
after i run "git svn dcommit".
Is it a expected behavior or is it a bug?
If it's not a bug, I would have a headache about this as i have a
small team using git-svn. Everytime i pull all the changes from my
colleagues (they clone from my git repo) and then dcommit (sync to
SVN). All the hashcode are changed and i need all my colleague in the
team to rebase again. that means they need do something like reset
some commits (which are local commit to their git repo only) and pull
again from my repo after svn sync.

I hope i can describe the scenario clearly and anybody has an idea
about that wheather on the git-svn config or the git-svn workflow.


You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to