On 8/29/21 5:07 PM, Junio C Hamano wrote:
This is one of the reasons why "rebase" (especially "rebase -i") may want to insist starting at the top-level of the working tree, like "git bisect" does. Because running the command from a subdirectory works most of the time until it doesn't, people tend to complain why they should go up to the top-level before they can run the command. And this is why---it causes end-user confusion.
But there's no confusion here - git doesn't have to delete the directory and recreate it, but it does it anyway.
So this is just a bug that git disturbs users more than it should. Yuri
