Re: git rebase command and docs questions
- From
- Eugene Sajine <euguess@gmail.com>
- Date
- Apr 9, 2010, 20:51 UTC
- Message-ID
- <p2m76c5b8581004091351o8ed7877ch1361f0089d3bdf79@mail.gmail.com>
- In-Reply-To
- <r2mfabb9a1e1004091337w8ec2b721y3a5082d5e0f5925c@mail.gmail.com>
On Fri, Apr 9, 2010 at 4:37 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
Show 13 quoted lines
> Heya, > > On Fri, Apr 9, 2010 at 20:49, Eugene Sajine <euguess@gmail.com> wrote: >> But, in “git rebase –onto master next topic” the meaning of the “next >> topic” parameters is different: as I understand, it actually specifies >> a range of commits from next to topic, because –onto changes the way >> the whole command is working, but it is not clarified in help. Is that >> correct understanding? > > I've never been able to remember how rebase --onto works, perhaps if > we actually let users specify a range it would be more intuitive? > > $ git rebase next..topic master
I thought about it too. Even with the old syntax:
git rebase --onto master next..topic
at least as a second option the whole command would be much more understandable for users. Currently, it fails with such range.
Thanks, Eugene