Friday, November 22, 2013

Making ‘git rebase’ Safe on OS X

Alexander Rinass:

When performing a large rebase with several commits and many changed files, the rebase process can randomly abort, stating that there are uncommitted changes and rebase cannot continue. However, a “git status” does not report any changes.


The problem has been tracked down to the revisiond daemon of the OS X Versions feature, which detects file changes and seems to somehow alter the file system info of the file, causing a rebase step to fail as it then detects changes.

Comments RSS · Twitter

Leave a Comment