From: Peter Harris Date: Tue, 25 Aug 2009 22:49:33 GMT Subject: Re: git svn messages Message-ID: In-Reply-To: <43d8ce650908251531n397ba6e1xe71e80d7b8a08344@mail.gmail.com> On Tue, Aug 25, 2009 at 6:31 PM, John Tapsell wrote: > Hi all, > >  When doing git svn dcommit, the messages that it gives are, well, > frightening :-) Some moreso than others, depending on your level of familiarity with git. :-) > It's full of things like: > >> No changes between current HEAD and refs/remotes/git-svn > > No changes?  What's gone wrong?  Why can't it find any changes?.. Because you aren't working from a branch-point older than your current refs/remotes/git-svn. I suppose one could misinterpret that as a bidirectional "no changes". Still, the message doesn't contain a scary prefix like "Error:" or even "Warning:". It's just informational. >> Resetting to the latest refs/remotes/git-svn > > That doesn't sound good.  Why did it have reset? Because the newly created svn commits are a different DAG from your former DAG (which contained git commits that weren't in svn yet), even though the tree contents are the same. The way git-svn tells the rest of git about this change is by running the "git reset" command. You can run "gitk" before you run "git svn dcommit", then hit refresh (F5, I believe) after "git svn dcommit" is done to get a more visual idea of what is going on. Peter Harris