On Sun, 14 Mar 2010, Junio C Hamano wrote:
There's already a test for rebasing on a previously detached HEAD. The form "git rebase -i HEAD~2" specifies a non-branch upstream, but doesn't take the branch argument which is the point of the change.What I meant was that if you prefer to work on a detached HEAD (and I sometimes do), then your HEAD would likely to be detached already when you run rebase. IOW, I would expect that git checkout HEAD^0 ... perhaps do something, perhaps do nothing, here ... git rebase -i HEAD~2 would be a lot more natural thing to do, and in that case you do not need to say HEAD^0 there.
That functionality already works. It's certainly possible to do it as you describe, but why require the extra step? git-rebase already supports detaching as part of its behavior, but rebase -i does not. It may seem nitpicky, but it's asymmetric and occasionally it's handy syntax. -- 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