On Tue, Nov 10, 2009 at 5:23 PM, Pascal Obry <pascal@xxxxxxxx> wrote: > $ git svn rebase > fatal: Invalid revision range > d2cf08bb67e4b7da33a250127aab784f1f2f58d3..refs/remotes/svn/trunk > rev-list --pretty=raw --no-color --reverse > d2cf08bb67e4b7da33a250127aab784f1f2f58d3..refs/remotes/svn/trunk --: command > returned error: 128 Is d2cf08bb67e4b7da33a250127aab784f1f2f58d3 a valid revision? (git log d2cf08bb67e4b7da33a250127aab784f1f2f58d3). Is refs/remotes/svn/trunk valid? (git log refs/remotes/svn/trunk). It seems like a strange problem. > Using v1.6.4 instead I have no problem. Any idea to track this problem down? You could try using git bisect to figure out which exact commit to git.git created the problem. Avery -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html