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
2. git svn dcommit (if no conflict in Step 1)
3. git svn rebase (after dcommit) <- the same commit's hashcode is now
"xyz0987" which was "abcd1234")

It will be a problem if i have a dedicated person/repo to sync the
team changes (which were git commit) into SVN and others in the team
using git only.
They will need to reset and rebase every time something is synced/
checked in to the SVN.

On Oct 14, 11:23 am, David Aguilar <> wrote:
> 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:
> > 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
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to