I've seen this mentioned on here in the past, either by yourself or maybe Alan, and I'm a bit curious as to what actually happens?
I cant say I have seen it cause me any problems so far when using git-svn (git cloned from the git mirror, then git-svn initialised and rebased against svn). Indeed, git-svn doesnt seem to care at all when an incoming commit log doesnt match the message for a local commit of the same changes, which is a situation I often tend to provoke in checkouts im using by changing a message before dcommitting it from another workspace I have applied it to. Do you have any special sauce in your git workflow? not using git-svn? Robbie On 10 August 2012 19:35, Andrew Stitcher <[email protected]> wrote: > On Fri, 2012-08-10 at 19:24 +0100, Gordon Sim wrote: > > ... > > > > You can retrospectively edit the commit log for svn if you like. > > I hope that isn't something many people do: It has the strong > possibility to totally screw up the synchronisation with git depending > on exactly when the synchronising is done. > > So although it would look ok in svn it be end up a mess in git. > > Personally I'm more dependent on git for my work, so this bothers me a > lot. > > Andrew > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
