{"thread":{"id":"22616","subject":"git-svn writing mergeinfo","startedAt":"2010-02-11T17:10:07Z","lastAt":"2010-02-11T17:10:07Z","messageCount":1,"participants":["Stephen Haberman"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"134242","messageId":"20100211111007.b04e8f26.stephen@exigencecorp.com","threadId":"22616","inReplyTo":null,"subject":"git-svn writing mergeinfo","fromName":"Stephen Haberman","fromEmail":"stephen@exigencecorp.com","sentAt":"2010-02-11T17:10:07Z","receivedAt":"2010-02-11T17:10:07Z","isPatch":false,"sender":{"key":"stephen@exigencecorp.com","avatar":"https://gravatar.com/avatar/23b93ad70a06ce53505f17ddba65176edbcfb6588e7a4c1a2dca04aaf0a6aff1?d=mp&s=160"},"body":"Hi,\n\nI just stumbled across the mergeinfo support coming in git 1.7. Looks\nlike very awesome stuff for those of us using git as a better-than-svn\nsvn client.\n\nTrying 1.7-rc2 locally, I can see mergeinfo properties getting read.\n\nBut the killer feature of doing a git merge --no-ff/git svn dcommit\ndoesn't seem to generate and write mergeinfo properties back to svn.\nUnless I'm doing something wrong.\n\nAre there any plans for this, even if svn's model means only in\na limited form? E.g. no multi-parent/reflective/etc.\n\nI was really surprised to learn that Bazaar writes mergeinfo back to\nsvn [1]--I had assumed a DAG-based DVCS would just never get that good\nof svn interop. So, seeing that Bazaar does something like this gives\nme hope that git could do it eventually as well.\n\nThanks,\nStephen\n\n[1]: http://wiki.bazaar.canonical.com/BzrForeignBranches/Subversion\n"}]}