Hi,
On Tue, 19 Feb 2008, Björn Steinbrink wrote:
> when there's nothing to rebase (ie. upstream..branch is empty), rebase
> fails to find any commits to rebase and correctly says "Nothing to do",
> but when --onto is given, we already did a "reset --hard" to newbase, so
> it already _did_ something.
Yes, it did something. But if you had that:
A - B - C - D - E
\
F
your HEAD was E, and you said "git rebase --onto F E" what exactly do you
want it to do? There is no commit between E and E, so it rebases
_nothing_ onto F. Which means that F should be your new state.
Unless I am missing something critical in your mail.
> As rebase also shows a "fatal: Not a range", during the operation, I
> assume that this is an actual bug and not just a plain user error.
That message is probably a bug, then.
Ciao,
Dscho
P.S.: I was being corrected some time ago on the same typo: "to lose"
means to get rid of something unintentionally, "to loose" does not exist,
and "to loosen" means to make something less tight.
