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

Re: [RFC] Applying a graft to a tree and "rippling" the changes through the history

From
Junio C Hamano <junkio@cox.net>
Date
Nov 7, 2005, 01:45 UTC
Message-ID
<7vll01ut6j.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<436E85DA.1080904@michonline.com>
Ryan Anderson <ryan@michonline.com> writes:
> I've written a tool that will take a single commit, add it as a parent
> of another commit, and recreate the history above that second commit in
> a fully compatible manner.

I think the procedure is reproducible, which is a very nice property to have for a tool like this, but I am not sure what you mean by "in a fully compatible manner". What are you compatible with?

Also another rhetorical, tongue-in-cheek question. What is your plan to ripple the graft through to update signed tags? ;-)

Previous: Randal L. SchwartzNext: Ryan Anderson
Message 3 of 5 in “[RFC] Applying a graft to a tree and "rippling" the changes through the history”
  1. Ryan AndersonNov 6, 2005
  2. Randal L. SchwartzNov 6, 2005
  3. Junio C HamanoNov 7, 2005
  4. Ryan AndersonNov 7, 2005
  5. Matthias UrlichsNov 18, 2005

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.