Junio C Hamano wrote: > You can also specify the commit at the end of the history to be > rebased (very useful while trial runs to see where a series should > apply): > > git rebase foo ":/Add B" > > This is already handled properly because it first gets turned into > an object name $orig_head and then we use it (without ^0) to update > the ORIG_HEAD. Correct, but what sense does it make unless <branch> is a ref to update? $ git rebase master :/v1.8.1 First, rewinding head to replay your work on top of it... Fast-forwarded :/v1.8.1 to master. Huh? The message is wrong, and no end-user can figure out what happened. > Even after this patch, there is > > git checkout -q "$onto^0" > > when detaching the HEAD to that commit. Can that peeling be dropped > now (I am not suggesting to drop it in this patch)? Yeah, that can be dropped. > What would happen when you are given "--onto :/f...o" is somewhat > interesting, but that may be a separate topic, I think. At that > point, it is probably in the realm of "don't do it then" ;-) The utility of this very series can be questioned. I've rarely wanted to use the :/fommery with rebase, so this mostly an exercise in "theoretical correctness" (something I usually stay away from). -- 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