git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Sajine <euguess@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: git@vger.kernel.org, Eugene Sajine <euguess@gmail.com>
Subject: Re: git rebase command and docs questions
Date: Fri, 9 Apr 2010 16:51:06 -0400	[thread overview]
Message-ID: <p2m76c5b8581004091351o8ed7877ch1361f0089d3bdf79@mail.gmail.com> (raw)
In-Reply-To: <r2mfabb9a1e1004091337w8ec2b721y3a5082d5e0f5925c@mail.gmail.com>

On Fri, Apr 9, 2010 at 4:37 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> 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

  reply	other threads:[~2010-04-09 20:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 18:49 git rebase command and docs questions Eugene Sajine
2010-04-09 20:37 ` Sverre Rabbelier
2010-04-09 20:51   ` Eugene Sajine [this message]
2010-04-09 21:11   ` Junio C Hamano
2010-04-09 21:23     ` Sverre Rabbelier
2010-04-10 22:30       ` Eugene Sajine
2010-04-10 22:32         ` Sverre Rabbelier
2010-04-10 22:40           ` Eugene Sajine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=p2m76c5b8581004091351o8ed7877ch1361f0089d3bdf79@mail.gmail.com \
    --to=euguess@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=srabbelier@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).