{"thread":{"id":"20735","subject":"git svn messages","startedAt":"2009-08-25T22:31:05Z","lastAt":"2009-08-25T22:49:33Z","messageCount":2,"participants":["John Tapsell","Peter Harris"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"121757","messageId":"43d8ce650908251531n397ba6e1xe71e80d7b8a08344@mail.gmail.com","threadId":"20735","inReplyTo":null,"subject":"git svn messages","fromName":"John Tapsell","fromEmail":"johnflux@gmail.com","sentAt":"2009-08-25T22:31:05Z","receivedAt":"2009-08-25T22:31:05Z","isPatch":false,"sender":{"key":"johnflux@gmail.com","avatar":"https://gravatar.com/avatar/25f70d4c0f96396b84a2e34bcd9bdc233462c7b4be29b5fdca8266fc53f30b0c?d=mp&s=160"},"body":"Hi all,\n\n  When doing git svn dcommit, the messages that it gives are, well,\nfrightening :-)\n\nIt's full of things like:\n\n> No changes between current HEAD and refs/remotes/git-svn\n\nNo changes?  What's gone wrong?  Why can't it find any changes?..\n\n> Resetting to the latest refs/remotes/git-svn\n\nThat doesn't sound good.  Why did it have reset?  Were the errors to\ngreat for it to continue, so it had to reset?\n\nJohn\n"},{"id":"121760","messageId":"eaa105840908251549o6d53fe9fnb1dfc00395ad36f4@mail.gmail.com","threadId":"20735","inReplyTo":"43d8ce650908251531n397ba6e1xe71e80d7b8a08344@mail.gmail.com","subject":"Re: git svn messages","fromName":"Peter Harris","fromEmail":"git@peter.is-a-geek.org","sentAt":"2009-08-25T22:49:33Z","receivedAt":"2009-08-25T22:49:33Z","isPatch":false,"sender":{"key":"git@peter.is-a-geek.org","avatar":null},"body":"On Tue, Aug 25, 2009 at 6:31 PM, John Tapsell wrote:\n> Hi all,\n>\n>  When doing git svn dcommit, the messages that it gives are, well,\n> frightening :-)\n\nSome moreso than others, depending on your level of familiarity with git. :-)\n\n> It's full of things like:\n>\n>> No changes between current HEAD and refs/remotes/git-svn\n>\n> No changes?  What's gone wrong?  Why can't it find any changes?..\n\nBecause you aren't working from a branch-point older than your current\nrefs/remotes/git-svn. I suppose one could misinterpret that as a\nbidirectional \"no changes\". Still, the message doesn't contain a scary\nprefix like \"Error:\" or even \"Warning:\". It's just informational.\n\n>> Resetting to the latest refs/remotes/git-svn\n>\n> That doesn't sound good.  Why did it have reset?\n\nBecause the newly created svn commits are a different DAG from your\nformer DAG (which contained git commits that weren't in svn yet), even\nthough the tree contents are the same. The way git-svn tells the rest\nof git about this change is by running the \"git reset\" command.\n\nYou can run \"gitk\" before you run \"git svn dcommit\", then hit refresh\n(F5, I believe) after \"git svn dcommit\" is done to get a more visual\nidea of what is going on.\n\nPeter Harris\n"}]}