git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
PDPatrick Doyle <wpdster@gmail.com>
Date
Aug 3, 2007, 01:44 UTC
Message-ID
<e2a1d0aa0708021844y251273a4q9af44e066cca2b42@mail.gmail.com>
In-Reply-To
<46B23415.8030008@vilain.net>
Show 11 quoted lines
> 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.

Thanks Sam, Now I see the noMetadata option. I'll give that try and see how much trouble I get myself in.

As I was thinking about this some more, I started wondering if perhaps the information could be stored in a .git-svnid file, that was versioned on the subversion server as well as in the local git repository.

I'll have to think through the implications of your explanation in the mean time.

--wpd
Previous: Sam Vilain
Message 3 of 3 in “Why does git-svn dcommit rewrite the log messages?”
  1. Patrick DoyleAug 1, 2007
  2. Sam VilainAug 2, 2007
  3. Patrick DoyleAug 3, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.