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

Re: [PATCH/RFC 0/2] rebase: add switches to control todo-list setup

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 23, 2019, 01:21 UTC
Message-ID
<xmqq4l6p7bz7.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<623d6ebd-60c4-916d-6295-4c648dbf3932@gmail.com>
Phillip Wood <phillip.wood123@gmail.com> writes:
> Doing "git rebase -i master" and then editing the todo list has the
> side effect of rebasing the branch. Often I find I want to amend or
> reword a commit without rebasing (for instance when preparing a
> re-roll).

I am not sure what you mean by "not rebasing". Are you talking about --keep-base that uses the same --onto as the previous?

I think that is often desired, but I do not think it has much to do with the topic of the proposal these two patches raises.

And that (i.e. "this has nothing to do with the choice of 'onto'") was why I used the casual "rebase -i master" in my illustrations.

Previous: Denton LiuNext: Phil Hord
Message 9 of 11 in “rebase: add switches to control todo-list setup”
  1. 0/2 rebase: add switches to control todo-list setupPhil Hord, Apr 22, 2019
  2. 1/2 rebase: add switches for drop, edit and rewordPhil Hord, Apr 22, 2019
  3. 2/2 rebase: add --break switchPhil Hord, Apr 22, 2019
  4. Junio C HamanoApr 22, 2019
  5. Phillip WoodApr 22, 2019
  6. Phil HordApr 22, 2019
  7. Phil HordApr 22, 2019
  8. Denton LiuApr 22, 2019
  9. Junio C HamanoApr 23, 2019
  10. Phil HordApr 23, 2019
  11. Phil HordApr 22, 2019

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.