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

Re: [PATCH] Add git-graft-ripple, a tool for permanently grafting history into a tree.

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 23, 2005, 15:40 UTC
Message-ID
<Pine.LNX.4.63.0511231638080.8993@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<20051123135150.GA16995@mythryan2.michonline.com>
Hi,
On Wed, 23 Nov 2005, Ryan Anderson wrote:
> For some reason, my gut says that this goes too far.  I'm having a hard
> time pinning down a way to explain that.
I can pin down what my gut says:
- the old commits still exist, so the links are not invalid
- the commit message is signed off as is
- the process to find the correct new SHA1 is not straight-forward, i.e.
  one would need to introduce a recursion where now suffices a simple
  linear loop.

Ciao, Dscho

Previous: Randal L. SchwartzNext: Linus Torvalds
Message 6 of 7 in “Add git-graft-ripple, a tool for permanently grafting history into a tree.”
  1. Add git-graft-ripple, a tool for permanently grafting history into a tree.Ryan Anderson, Nov 22, 2005
  2. Linus TorvaldsNov 23, 2005
  3. Andreas EricssonNov 23, 2005
  4. Ryan AndersonNov 23, 2005
  5. Randal L. SchwartzNov 23, 2005
  6. Johannes SchindelinNov 23, 2005
  7. Linus TorvaldsNov 23, 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.