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

Re: Advice on edits to git-rebase man page

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 5, 2015, 21:29 UTC
Message-ID
<xmqqmw4sjbcm.fsf@gitster.dls.corp.google.com>
In-Reply-To
<vpq1tm412dk.fsf@anie.imag.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
Show 9 quoted lines
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Perhaps something like this instead?
>>
>>     git-rebase - Rebuild a branch on top of a different commit
>
> I would say "Replay history on top of a different commit" instead.
> "Rebuild" may be misleading (it's not "build" as in "compile & link"),
> and the rebased history does not technically have to be a branch.

I am fine if the description were "replay history and repoint the branch tip to the result"; the fact that branch tip moves is an important part of the semantics of the command.

Otherwise, you cannot cleanly capture why we have rebase and cherry-pick (which can do ranges these days).

Previous: Matthieu MoyNext: Matthew Brett
Message 5 of 7 in “Advice on edits to git-rebase man page”
  1. Matthew BrettFeb 4, 2015
  2. Matthieu MoyFeb 5, 2015
  3. Junio C HamanoFeb 5, 2015
  4. Matthieu MoyFeb 5, 2015
  5. Junio C HamanoFeb 5, 2015
  6. Matthew BrettFeb 18, 2015
  7. Matthew BrettFeb 23, 2015

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.