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

Re: [PATCH] Attempt to improve git-rebase lead-in description.

From
Jakub Narebski <jnareb@gmail.com>
Date
Feb 18, 2007, 02:21 UTC
Message-ID
<er8d34$ssm$1@sea.gmane.org>
In-Reply-To
<20070217093150.GA25871@spearce.org>
Shawn O. Pearce wrote:
> +
> +The commits that were previously saved into the temporary area are
> +then reapplied to the current branch, one by one, in order.

Which is true for git-format-patch/git-am --3way driven "git rebase", but not for git-merge driven "git rebase --merge".

The description is certainly more user-friendly, but I'd rather it avoid mentioning saving to temporary area.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Shawn O. PearceNext: Shawn O. Pearce
Message 2 of 3 in “Attempt to improve git-rebase lead-in description.”
  1. Attempt to improve git-rebase lead-in description.Shawn O. Pearce, Feb 17, 2007
  2. Jakub NarebskiFeb 18, 2007
  3. Shawn O. PearceFeb 18, 2007

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.