git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git rebase command and docs questions

From
ESEugene Sajine <euguess@gmail.com>
Date
Apr 9, 2010, 18:49 UTC
Message-ID
<h2j76c5b8581004091149y9f5f93a8o5f11b3ffc657623@mail.gmail.com>
Hi,
I have few questions about rebase and its help content:
1. In case of this situation
o---o---o---o---o  master
        \
         o---o---o---o---o  next
                          \
                           o---o---o  topic

“git rebase master topic” says: The current branch topic is up-to-date.

This message seems to be confusing and even incorrect. The actual problem, as I understand, is that topic branch is not a direct descendant of the master branch, therefore “git rebase –onto master next topic” should be used instead. Is there a way for git to identify this problem more correctly and print more helpful error message?

2. The rebase help is a bit confusing in its “–onto” option part.
Initially help says that the form:
git rebase master topic
is a shorthand for git checkout topic, git rebase master

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?

3. The part of help from “Another example of --onto option is to
rebase part of a branch.” Is actually demonstrating absolutely the
same thing as the one before with the only difference that in the
second example the master has not advanced. There was probably some
different intention, but currently it looks like confusing
duplication.

Thanks, Eugene

Next: Sverre Rabbelier
Message 1 of 8 in “git rebase command and docs questions”
  1. Eugene SajineApr 9, 2010
  2. Sverre RabbelierApr 9, 2010
  3. Eugene SajineApr 9, 2010
  4. Junio C HamanoApr 9, 2010
  5. Sverre RabbelierApr 9, 2010
  6. Eugene SajineApr 10, 2010
  7. Sverre RabbelierApr 10, 2010
  8. Eugene SajineApr 10, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.