[git-users]

*لمتابعه كل اخبار الكمبيوتر و تكنولوجيا المعلومات وايضا صفحتنا الرومانسيه ع الفيس بوك يمكنكم التواصل معنا من هنا * -- 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] git-svn hashcode difference before and after dcommit

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 f

Re: [git-users] git-svn hashcode difference before and after dcommit

On Oct 13, 2011, at 8:12 PM, abgalphabet wrote: > 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? expected behavior. do you use git svn rebase? here's a good writeup: http://learn.github.com/p/git

[git-users] Re: git-svn hashcode difference before and after dcommit

Yes. my workflow of git-svn usage is (say i have a local git commit with hash "abcd1234" need to check into SVN) 1. git svn rebase (before dcommit) <- at this time hashcode is "abcd1234" 2. git svn dcommit (if no conflict in Step 1) 3. git svn rebase (after dcommit) <- the same commit's hashcode i