Re: [PATCH 3/3] rebase: use peel_committish() where appropriate

Ramkumar Ramachandra artag...@gmail.com writes: 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

Re: [PATCH 3/3] rebase: use peel_committish() where appropriate

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

[PATCH 3/3] rebase: use peel_committish() where appropriate

The revisions specified on the command-line as onto and upstream arguments could be of the form :/quuxery; so, use peel_committish() to resolve them. The failing tests in t/rebase and t/rebase-interactive now pass. Signed-off-by: Ramkumar Ramachandra artag...@gmail.com --- git-rebase.sh

Re: [PATCH 3/3] rebase: use peel_committish() where appropriate

Ramkumar Ramachandra artag...@gmail.com writes: The revisions specified on the command-line as onto and upstream arguments could be of the form :/quuxery; so, use peel_committish() to resolve them. The failing tests in t/rebase and t/rebase-interactive now pass. You can also specify the

[PATCH 3/3] rebase: use peel_committish() where appropriate

The failing tests in t/rebase and t/rebase-interactive pass as a result. Signed-off-by: Ramkumar Ramachandra artag...@gmail.com --- git-rebase.sh | 6 +++--- t/t3400-rebase.sh | 2 +- t/t3404-rebase-interactive.sh | 2 +- 3 files changed, 5 insertions(+), 5