Re: Why does git-svn dcommit rewrite the log messages?

From: Sam Vilain <sam@vilain.net>
Date: Aug 2, 2007, 19:44 UTC
Message-ID: <46B23415.8030008@vilain.net>
In-Reply-To: <e2a1d0aa0708011419m1f6cb323ge9e93680147a298@mail.gmail.com>

Patrick Doyle wrote:

Show 15 quoted lines

> I see that it appends text to the log messages with the SVN repository
> revision and ID.  Does it do that because:
>
> 1) That's the _only_ way to keep git & svn in sync
> If so, then I guess I'm out of luck.  But it seems (to my
> inexperienced eye) to make branching impossible in git -- as soon as I
> do a "git-svn dcommit", I lose the commit on which my branch was
> originally based.  Or, am I missing something?
>
> 2) That was the simplest way to keep them in sync at the time git-svn
> was written and it hasn't bothered anybody enough to go back and fix
> it.
> If so, I'd be glad to see what I could do to fix it.  I would also
> appreciate any pointers folks might care to give to get me started.
>

Primarily it's so that the person who pushed via dcommit and people who sync via git-svn fetch get the same commit ID (assuming they are both using the same authors map).

It might be possible to store the extra information needed to recreate exactly the original git commit in SVN revision properties, but this would need to be implemented once and basically not changed after that.

You can disable this behaviour, but you'll end up with duplicate commits.

Sam.