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

Re: [PATCH] Documentation: Transplanting branch with git-rebase --onto

From
Junio C Hamano <junkio@cox.net>
Date
Nov 6, 2006, 22:53 UTC
Message-ID
<7v4ptcchli.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200611061912.46436.jnareb@gmail.com>
Jakub Narebski <jnareb@gmail.com> writes:
Show 9 quoted lines
> Added example of transplantig feature branch from one development
> branch (for example "next") into the other development branch (for
> example "master").
>
> [jn: with a little help from Junio]
>
> Signed-off-by: Jakub Narebski <jnareb@gmail.com>
> ---
> What about this?

I agree with Carl that the original example of --onto was not clear why it is a good thing, so I am inclined to follow his suggestion and drop the original example and keep your second one yanked from your try#1 patch when committing, if it is Ok with you.

Previous: Jakub NarebskiNext: Jakub Narebski
Message 5 of 8 in “Documentation: Two more git-rebase --onto examples”
  1. Documentation: Two more git-rebase --onto examplesJakub Narebski, Nov 4, 2006
  2. Junio C HamanoNov 5, 2006
  3. Jakub NarebskiNov 5, 2006
  4. Documentation: Transplanting branch with git-rebase --ontoJakub Narebski, Nov 6, 2006
  5. Junio C HamanoNov 6, 2006
  6. Jakub NarebskiNov 6, 2006
  7. Carl WorthNov 6, 2006
  8. Junio C HamanoNov 6, 2006

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.