{"thread":{"id":"31501","subject":"git-svn mergeinfo","startedAt":"2012-09-11T12:01:01Z","lastAt":"2012-09-11T12:01:01Z","messageCount":1,"participants":["Brice Goglin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"198771","messageId":"504F27FD.6020204@gmail.com","threadId":"31501","inReplyTo":null,"subject":"git-svn mergeinfo","fromName":"Brice Goglin","fromEmail":"brice.goglin@gmail.com","sentAt":"2012-09-11T12:01:01Z","receivedAt":"2012-09-11T12:01:01Z","isPatch":false,"sender":{"key":"brice.goglin@gmail.com","avatar":null},"body":"Hello,\n\nI am using git 1.7.10.4 from Debian. I just tried svn.pushmergeinfo and\nit seems to have worked fine, great.\n\nNow I am trying to understand what the doc says about this:\n\"Currently, this can only be done when dcommitting non-fast-forward\nmerges where all parents but the first have already been pushed into SVN.\"\n\n\"all parents but the first have already been pushed into SVN\" means that\nmerging A into B requires to dcommit in A first, right?\n\"non-fast-forward\" means that both branches got some commits since the\nlast merge, right?\n\nCould we add an example after the above doc sentence? Something like\n\"For instance, if merging SVN branch B into A, make sure you dcommit A\nfirst, and check that both A and B got new commits since the last merge\n(or since B was created from A)\".\n\nBrice\n"}]}