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

Re: git rebase command and docs questions

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Apr 9, 2010, 20:37 UTC
Message-ID
<r2mfabb9a1e1004091337w8ec2b721y3a5082d5e0f5925c@mail.gmail.com>
In-Reply-To
<h2j76c5b8581004091149y9f5f93a8o5f11b3ffc657623@mail.gmail.com>
Heya,
On Fri, Apr 9, 2010 at 20:49, Eugene Sajine <euguess@gmail.com> wrote:
Show 5 quoted lines
> 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
-- 
Cheers,

Sverre Rabbelier
Previous: Eugene SajineNext: Eugene Sajine
Message 2 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.